We've used the experience gained with Migrate 1.0 and rewritten the module from the ground up in Migrate 2.0 for Drupal 7. We will now begin backporting Migrate 2.0 to Drupal 6. One critical note - there will be no automated upgrade path from 1.0 to 2.0 (the architecture is simply too different) - if you have existing projects using Migrate 1.0, you should stick with that.

Comments

mikeryan’s picture

BTW, "we will now begin backporting" was expressed a little too optimistically - first we're doing some cleanup and refactoring of the D7 code (things like #753292: Factor out common bits of rollback/import), it'll be a lot easier to do it now in one branch than to do it later in two.

mikeryan’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
Assigned: Unassigned » mikeryan

I've cut the DRUPAL-6--2 branch and populated it with straight copies of the D7 files - it's a long way from running at all, so please don't bother trying to check it out before we say it's ready for initial evaluation here.

mikeryan’s picture

FYI, the two primary issues remaining before backporting in earnest are:

#802264: Refactor map table support
#753284: Straighten out update scenarios

These involve significant refactoring, and thus would require a lot of extra work to backport individually after the initial backport is done.

mikeryan’s picture

Backport work has begun, and the basic infrastructure is ported, but there's still a ways to go around entities/fields. At the moment, focusing on simpletests to help guide the backport:

#392404: Develop simpletests for Migrate

mikeryan’s picture

Status: Active » Fixed

I finally fixed comment import on D6 this past weekend, so Migrate 2 on D6 is in sync with D7. Still some work to go before both are ready for an alpha release, but I can close this issue out.

ChrisBryant’s picture

Thanks for the updates here on the progress!

Status: Fixed » Closed (fixed)

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