Avenue to successful content migration testing

Drupal-to-Drupal migrations; importing content from CSVs or XML to populate a new site build; importing XML from an eBook as nodes for an online version of the book content, and so on are some of the areas where testing for correctness of content migration is critical.

On one of recent project, the source data is anything but consistent, so while a manual review of one migrated item might look correct, any number of other items could have problems. Adding to the challenge is that this is not a one-time migration, but a regular, nightly import of data, so we can't afford to have errors from the migration showing up in production.

Agenda:

• Scope of Drupal content migration testing.

• Various real time scenarios faced in Acquia while implementing migration.

• Testing content migration v/s drupal version migration.

• Various tools used to help automate migration testing.

• Things that should be avoided while testing migration.

• Importance of automated test and structure

• Method to be followed to plan these tests

• Best practices for making migration tests successful.

• What tools can help with a content migration

• Organizing (mapping) content, remember the difference between forests and trees

• Trying to answer few typical client questions with respect to Migrations -

  • How to ensure that data migration is successful?

  • How to ensure that data is migrated as per the requirement?

  • How to make sure that migrated data works well in the latest product?

  • How to validate that the migrated data is integrated in real world?

  • Is Data migration validation process scalable?

  • Is data migration validation process can be done within the allocated time?

• Solving time v/s content puzzle

• Few Test scenarios to ensure success!