Drupal campchicago2010.rachel.datamigration
Download as PPTX, PDF0 likes366 views
The document outlines a successful strategy for migrating 100,000 pages from a legacy CMS to Drupal, highlighting essential planning questions and tools for data migration. Key considerations include content types, taxonomies, URL restructuring, and effective file management. It emphasizes the importance of thorough testing and offers solutions like the Tw & Migrate and Node Import modules to facilitate the migration process.
![Create your own migration script[demo]](https://image.slidesharecdn.com/drupalcampchicago2010-rachel-datamigration-110211110604-phpapp01/85/Drupal-campchicago2010-rachel-datamigration-20-320.jpg)
Drupal campchicago2010.rachel.datamigration
- 1. Drupal MigrationMigrating 100,000 pages of contentFrom Legacy CMS to DrupalRachel JaroSolutions Architect at PrometSourcewww.prometsource.com
- 2. OverviewWe’ll talk about:Successful migration recipeCommon questions you should be asking before you startTop 3 tools to do migration in DrupalIssuesTools to use in URL RewritingFile management Comparison in D6TestingDeploying Solution
- 3. Data Migration “Data migration solutions extract data from a source system, correct errors, reformat, restructure and load the data into a replacement target system”. It sounds simple, but poorly managed data migration is the most common cause of failure in implementing a replacement system. -- Gershon Pick, March 2001
- 6. Plan: What to AskNode types (Content separation, fields)Do you want to separate contents into pages, articles, biography, news, etc.What fields are needed for each node?Who can access it?Do you really need that content type? Or can we just use taxonomies instead for similar contents.
- 7. Plan: What to AskTaxonomy (Categorization, tags)Do you need to categorize nodes? Would you need different access?What kind of taxonomy groups or vocabularies you would need?Permission (per nodes) and User RolesWho are going to use the site? What are particularly their access rights?
- 8. Plan: What to AskNew URL mappingDo you need to make SEO friendly URLs?Files, files permissions and file directoryDo you need advance file management or document management tool?Do you need simpler solutions? How simple is that. Do you need access rights for each folder?Do you need browser type interface to access them?What kind of files do you need to store? Images, pdfs?
- 9. Build
- 10. RequirementsUse CSV files to import dataDivide migration into group or sectionsMap and replace old URL to SEO friendly URLBefore: 05-200.htm
- 11. Data in CSV ExampleDecember 13, 2005 3:39:54 PM||||||||||December 13, 2005||||||||||Report Spotlights Need for Reform in Jackpot Jurisdictions||||||||||/press/releases/2005/december/||||||||||05-200||||||||||{UUID}|||||||||| Economics^^^^^^^^^^Economy ||||||||||<p>LoremIpsum is simply dummy text of the printing and typesetting industry. LoremIpsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. </p><p>LoremIpsum is simply dummy text of the printing and typesetting industry. LoremIpsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. </p>$$$$$$$$$$Separator: ||||||||||End of Row: $$$$$$$$$$
- 12. Content Type DivisionExample: CNN.comDivide migration sequences into US, World, Politics, Justice, etc
- 13. Solutions/ToolsTW and Migrate modules Combonode_import()Drush + custom script
- 14. TW & Migrate Module Combohttp://drupal.org/project/twSupports Migrate module to run views of source datahttp://drupal.org/project/migratea flexible framework for migrating content
- 15. Migrate ModuleFeatures:users browse their legacy data using viewssupport for creating Drupal nodes, users, and comments is includedhooks permit migration of other types of content.provides a dashboard for running mini migrationsDrush support
- 16. Why I did not choose migrateImporting to mysql was not an option. CSV were used insteadCannot map old URL to new URL
- 17. node_import()http://drupal.org/project/node_importFeatures:Easy to learn, Point and clickUses CSV to upload contentsCan easily delete previous imported dataCan download errors when import failed for easy reference to fix issues
- 18. node_import() ProblemsI can’t define map old URL to new URLNo drush supportIt doesn’t save my old settings for a csv.
- 19. Drush + Custom scriptFlexibility - I can do whatever I want with the data
- 20. Create your own migration script[demo]
- 22. File ManagementClient requirementsIntuitiveHas wysiwyg supportAccess control – upload, edit, delete, revise files by different rolesRevision control – optional but good to haveLimited time!
- 23. File Management Modules*DbFm was not included due to problems encountered during tests in D6
- 25. URLs Rewriting SolutionNot recommended.htaccessToo many URL to handle. Too much server loadRecommendedpathauto + path_redirect modulesautomated alias settings301 redirect setglobal redirectAdditional reference:http://acquia.com/blog/migrating-drupal-way-part-ii-saving-those-old-urls
- 28. Test, Test and did I say Test?Source: http://www.flickr.com/photos/paperpariah/2424107350/
- 29. Common problemsBroken linksMisconfigured pageEmpty pagesInvalid dateFile not found or orphan pagesPage formatTest when CACHE is on
- 30. Deployment
- 31. Deployment2 Ways to Deploy your data to live environmentAll at onceDivide and conquer
- 32. Deployment: Divide and ConquerExample: CNN Division
- 33. Deployment Mockup* shadow box is your migrated data’s production box* old CMS is still active at this time
- 34. DeploymentCoordination between the old CMS and Drupal
- 35. URL TestingDeployment Mockup* shadow box is your migrated data’s production box* replacing old CMS with Drupal
- 36. DeploymentProsLess risk, less stress Editors can do continues data entry dailyConsURL rewriting can be a trickyUpdating the production box with new content can be an arduous task
- 37. Deployment: Updating ProductionAutomationSVNDrush scripts to migrate contents from tester’s box to shadow boxDeploy – http://drupal.org/project/deployManualDocument configuration changesDocument database changes
- 38. RecapSDLC + AgileCommon questions you should be asking before you startTop 3 tools to do migration in DrupalTW & Migrate, node_import(), drushIssuesFile management Comparison in D6Tools to use in URL RewritingTestingDeployment Solution
- 39. Questions?