Manual testing: D6 File

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: drush en content filefield -y

D8: N/A

Place the manifest file in the D8 site root

Run the migration

From the D8 site root:
drush migrate-manifest --db-url=mysql://user:pass@source/source D6Manifest-File.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-File.yml

Compare post-migration settings

Files are going to be attached to specific content types, which will vary from site to site. If you're working with test data, be sure you've added a file field to a content type.

Main interface:
D6 config: admin/content/types
D8 config: admin/structure/types

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, 2222943 , in the Parent issue field!