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 upload -y
D8: N/A - File and Node enabled by default

Place the manifest file in the D8 site root

Download the latest manifest file.

Run the migration

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

Compare post-migration settings

Look at the nodes where upload had been used to attach files to content and compare values
Main interface:
D6 config:
/admin/settings/uploads
D8 config: per-content-type, per-field
Content for both: /admin/content

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

Comments

eliza411’s picture

Issue summary: View changes
benjy’s picture

  1. - d6_node:*
    

    Node is no longer a bundle migration and should simply be d6_node

  2. - d6_field_instance_defaults
    - d6_field_instance_per_form_display
    - d6_field_instance_widget_settings
    

    What are these doing in the manifest?

eliza411’s picture

StatusFileSize
new244 bytes

I can't recall what pointed toward including those migrations. I've updated the manifest. Thanks!

ultimike’s picture

Project: IMP » Drupal core
Version: » 8.x-dev
Component: Miscellaneous » migration system
bdone’s picture

Issue summary: View changes

i've updated instructions' migrate-manifest command to use the db-url option, per latest version of migrate-manifest.

ultimike’s picture

Issue summary: View changes
benjy’s picture

Status: Needs work » Fixed

Marking this issue fixed as I think we've reached a point now where the Drupal 6 to Drupal 8 issue path is stable enough that we can simply open individual issues as problems arise.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

phenaproxima’s picture

StatusFileSize
new268 bytes

The manifest file in #4 doesn't run smoothly, because the migrations are not listed in the correct order not every required migration (i.e., dependencies) is listed. The attached version fixes several errors for me.

phenaproxima’s picture

StatusFileSize
new280 bytes

Scratch that -- use this one. It will transfer the actual attachments as well.

phenaproxima’s picture

Issue summary: View changes
benjy’s picture

The manifest file in #4 doesn't run smoothly, because the migrations are not listed in the correct order.

Order should have no impact, they're loaded by the storage controller in the correct order.

phenaproxima’s picture

You're right. It's not that the order is wrong, it's that dependencies are missing. I'll update my comment.

phenaproxima’s picture

StatusFileSize
new304 bytes

Added the d6_user_picture_file migration to the manifest. Without this, users who have pictures don't get imported.