Migration to Drupal


Published on

Data migration to Drupal

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Migration to Drupal

  1. 1. Migration to Drupal <ul><li>Drupal </li></ul>
  2. 2. Migration of Data Data Migration <ul><li>Understanding your data
  3. 3. Migrating your data to a common format
  4. 4. Importing the data
  5. 5. Auditing and testing the results </li></ul>
  6. 6. Understanding your Data <ul><li>Understand the relationships between your data
  7. 7. Database schema
  8. 8. Entity relationship diagram (ERD)
  9. 9. Backup! </li></ul>
  10. 10. Migration to a common format <ul><li>Commonly understandable data between the source and target
  11. 11. XML, CSV, SQL
  12. 12. Process to import where necessary </li></ul>
  13. 13. Importing the data <ul><li>Using information gathered from - (1)Understanding Your Data
  14. 14. Use the data from - (2) Migrating to a common format
  15. 15. Process the data into database/required format </li></ul>
  16. 16. <ul>Auditing and testing the results </ul><ul><li>Review success of import
  17. 17. Test, test, test
  18. 18. Where necessary remove and re-import (utilise backups)
  19. 19. Learn from process to understand source and target </li></ul>
  20. 20. Migration to Drupal <ul><li>BACKUP!
  21. 21. Understanding your data
  22. 22. The Drupal database [Schema]
  23. 23. Migrate data to MySql
  24. 24. Process where necessary to align data databases enabling ease of insertion
  25. 25. Review processing/insertion
  26. 26. cont... </li></ul>
  27. 27. Migration to Drupal <ul><li>Expose the data to Drupal with Table Wizard
  28. 28. Import with Migrate
  29. 29. Auditing and testing the results (re-insert using Migrate where appropriate) </li></ul>
  30. 30. Backup <ul><li>Backup your database so if all goes wrong you have a working point to go back to.
  31. 31. Dump the database out and keep it safe! </li></ul>
  32. 32. Understanding your data <ul><li>Understanding your data
  33. 33. If within a database, understanding the relationships between your current data
  34. 34. How do you currently use/collect the data and what is the logic behind it? </li></ul>
  35. 35. The Drupal Database <ul><li>Schema
  36. 36. Understanding the core database </li></ul>
  37. 37. Migrate data into MySql <ul><li>Import data into MySql
  38. 38. Currently Table Wizard stipulates that to use the data, it must be within the Drupal database
  39. 39. Table Wizard module itself comes with an optional module called &quot;Table Wizard Import Delimited Files&quot; which can handle things like comma-separated values (CSV) files for you.
  40. 40. Caution with table names, no conflicts with Drupal </li></ul>
  41. 41. Process data to prepare for insert <ul><li>Draw connections between your data and where it would fit into Drupal database
  42. 42. Use the understanding of your data and the drupal data
  43. 43. The better you know your databases, the easier it is to connect </li></ul>
  44. 44. Preview transferral <ul><li>Ensure that your data is correct and that the data has transferred correctly
  45. 45. If any errors, retry your import or debug import </li></ul>
  46. 46. Expose the data to Drupal with Table Wizard <ul><li>Enable expose to views
  47. 47. Sort, analyse, list, alter data using views
  48. 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. </li></ul>
  49. 49. Import to Drupal core with Migrate <ul><li>You already know where you want the data to go fro previous analysis of your and Drupal database
  50. 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 </li></ul>
  51. 51. Auditing and testing results of import <ul><li>Test import of results
  52. 52. Do they match up with your aims/goals
  53. 53. Did the data import as expected? </li></ul>
  54. 54. Post migration <ul><li>Path redirect – Redirect pages that have already been indexed by search engines to the correct pages. (However, if you have a large amount of traffic it may be necessary to use apache to redirect)
  55. 55. Re-submit sitemaps to Webmaster Tools (Google, Yahoo, Bing). </li></ul>
  56. 56. Any questions? <ul><li>[email_address]
  57. 57. http://www.willhallonline.co.uk
  58. 58. Twitter: @willhallonline
  59. 59. LinkedIn: http://uk.linkedin.com/in/willhallonline
  60. 60. Drupal: willhallmusic
  61. 61. Drupal UK: willhall
  62. 62. Ubercart: willhall </li></ul>