![Migration to Drupal ,[object Object]](https://image.slidesharecdn.com/migrationtodrupal-100413155425-phpapp02/85/migration-to-drupal-1-320.jpg)
![Migration of Data Data Migration ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Migration to Drupal
Similar to Migration to Drupal (20)
More from Will Hall
More from Will Hall (16)
Recently uploaded
Recently uploaded (20)
Migration to Drupal
- 3. Migrating your data to a common format
- 5. Auditing and testing the results
- 8. Entity relationship diagram (ERD)
- 9. Backup!
- 11. XML, CSV, SQL
- 12. Process to import where necessary
- 14. Use the data from - (2) Migrating to a common format
- 15. Process the data into database/required format
- 17. Test, test, test
- 18. Where necessary remove and re-import (utilise backups)
- 19. Learn from process to understand source and target
- 22. The Drupal database [Schema]
- 23. Migrate data to MySql
- 24. Process where necessary to align data databases enabling ease of insertion
- 26. cont...
- 29. Auditing and testing the results (re-insert using Migrate where appropriate)
- 31. Dump the database out and keep it safe!
- 33. If within a database, understanding the relationships between your current data
- 34. How do you currently use/collect the data and what is the logic behind it?
- 36. Understanding the core database
- 38. Currently Table Wizard stipulates that to use the data, it must be within the Drupal database
- 39. Table Wizard module itself comes with an optional module called "Table Wizard Import Delimited Files" which can handle things like comma-separated values (CSV) files for you.
- 40. Caution with table names, no conflicts with Drupal
- 42. Use the understanding of your data and the drupal data
- 43. The better you know your databases, the easier it is to connect
- 45. If any errors, retry your import or debug import
- 47. Sort, analyse, list, alter data using views
- 48. Custom database. If you want a custom database, that is it. Provided you want to keep your old database structure, however, data that is relavant to Drupal should be migrated further.
- 50. Migrate natively supports importing nodes, taxonomy terms, users, comments, profile data, and even has some support for contributed modules such as FileField and Content Profile
- 52. Do they match up with your aims/goals
- 53. Did the data import as expected?
- 55. Re-submit sitemaps to Webmaster Tools (Google, Yahoo, Bing).