We need to create issues for each content migration listed below that contain:

Each issue should have a downloadable manifest file that includes only the content migration and its dependency chain. Where possible, the individual issue should also note when there are D6 settings that aren't imported because they have no home in D8.

Eventually, I think it would be beneficial to document the content migrations as handbook pages with the above information as well as paths to the location in the UI (or file paths, where applicable) to show where the data lived in D6 and where it lives now in D8. To Do: Create an example.

d6_aggregator_feed, d6_aggregator_item, d6_aggregator_settings #2221751
d6_block
d6_custom_block
d6_file

d6_profile_values
d6_taxonomy_term
d6_url_alias
d6_user_picture_file
d6_user

d6_node
d6_node_revision
d6_term_node
d6_term_node_revision
d6_comment
d6_upload
d6_menu
d6_menu_links (currently being developed, on #2178703: Migrate D6 menu links)

Want to help out? Either:

  1. Select a child issue from the right-hand column and follow the instructions!
  2. If there are any content migrations above that don't have issues yet, please create one. Use any of the previously-created child issues as an example.

Comments

eliza411’s picture

Issue summary: View changes
ultimike’s picture

Issue summary: View changes

Updated summary - struck out d6_taxonomy_term.

-mike

eliza411’s picture

Issue summary: View changes
eliza411’s picture

Issue summary: View changes
eliza411’s picture

Issue summary: View changes
eliza411’s picture

Issue summary: View changes
ultimike’s picture

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

Issue summary: View changes
ultimike’s picture

Issue summary: View changes
ultimike’s picture

Should we add menu items to this list as well?

-mike

Anonymous’s picture

Assigned: Unassigned »
jp.stacey’s picture

Issue summary: View changes

@ultimike the manifest for D6 Block seems to already contain an entry for d6_menu, so it's sort of already covered; but worth a separate issue? I'll create one as it can always be closed (also, I want to report an issue with it myself!)

jp.stacey’s picture

Issue summary: View changes
jp.stacey’s picture

Issue summary: View changes
jp.stacey’s picture

Issue summary: View changes
jp.stacey’s picture

Issue summary: View changes
benjy’s picture

Assigned: » Unassigned

I think we can close this issue and all child issues unless there is a specific issue on a child in which case we should re-purpose it to fix the problem at hand.

We've had a successful D6->D8 migration and i think we're at the point of wanting to fix individual bugs as they come up.

benjy’s picture

Status: Active » Fixed

Closing this issue 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.