Manual Testing: Taxonomy Term Fields

Follow-up to #2223795: Manual Testing: Taxonomy terms

Set up to test:

Important: See https://groups.drupal.org/node/398588 to get set up. This page also includes instructions for re-setting to a clean destination.

Ensure modules are enabled on the source and destination sites:
D6: Ensure "taxonomy" module is enabled.
D8: Ensure "taxonomy" module is enabled.

Place the manifest file in the D8 site root

Download the attached file (be sure to remove the "_.txt" - Drupal.org doesn't allow uploading of .yml files).

Run the migration

From the D8 site root:
drush migrate-manifest --db-url=mysql://user:pass@source/source D6Manifest-Taxonomy.yml

If you've updated/installed drush 7.x after July 16, 2014, you'll want to use:

drush migrate-manifest --legacy-db-url=mysql://user:pass@source/source D6Manifest-Taxonomy.yml

Compare post-migration settings

1. Ensure all the D6 vocabularies were migrated.
2. Ensure all D6 terms were migrated and placed in the proper vocabularies.
3. Note: the attached manifest will only test the migration of vocabularies and terms, it will not migrate term associations with nodes.
4. Ensure all D6 taxonomy vocabulary fields and field settings were migrated and placed in the proper vocabularies (/admin/structure/taxonomy/manage/%/overview/fields).

Success?

If your site migrates successfully, let us know with a comment on this issue. We'd love to hear details like:

• the size and complexity of the site you migrated
• performance observations
• any customizations you made to the migration manifest!

Problems?

Open a new issue as a normal priority support request. Describe what happened, including the exact text of error messages. Depending on the nature of the problem, someone may ask for a sample of the data you're trying to migrate or follow up with other questions.

Remember, too, that this is pre-Beta. The focus is on D6 core > D8 core, not custom work or contributed modules, so there may be portions of your site that need special consideration that won't get addressed at this point in the process.

Important: Please connect your issue to this issue when you create it by using entering this ticket number, 2223795 , in the Parent issue field!