Migration Documentation or Examples

I understand pulling together more resources on this (documentation, code, etc) to be an effort loosely planned to happen after a stable 2.0 release.

Any word on a projected date for a 'stable' 2.0 release? The folks at Phase2 continue to be somewhat sheepish about this.

Read here: https://drupal.org/node/2115321

At the webinar today, Mike Potter said he'll be publishing a project roadmap soon (I think he said "next week"?). Anyway, I expect that will lay out when Phase2 is planning to work on migrations. But this is no small undertaking! The Bucket Brigade has about 50 client sites on Open Atrium 1.x in production, so we'll likely be contributing to the effort building a migration path, once it starts. :-)

Added where i've looked.

Any chance we might progress on this issue? Plenty of users are seriously concerned about an upgrade path; see for instance this issue #2112977: Upgrade community site OpenAtrium, where the Ægir team is investigating the options for its Atrium 1 website...

Personally, I decided to adopt Open Atrium 1 back then because it was such an easy way to deploy an intranet. As a freelancer, I certainly don't have the time to write the necessary Migrate classes by myself, though I certainly could test them and propose patches once the upgrade effort has begun.

We have some basic scripts that we are currently testing. However, I don't want to get your hopes up. Any migration of an Open Atrium 1 site is going to be difficult just because of the nature of migrating from Drupal 6 to Drupal 7. Our Migrate scripts will only be examples that you'll likely need to modify for your specific site details.

@mpotter: Do you have an ETA for when those scripts will be shared? It'd be great if they could be in an independent project on Drupal.org so that the community can contribute and improve them. :-)

We don't want to release the first version until we have done some basic testing of them. Hopefully within the next couple of weeks, but I'm not promising any specific date. And yes, they will be an independent project, either on Drupal.org or on github.

Awesome, sounds good!

@mpotter: Any update on this? I have a client that is very interested in the release of this code and is willing (more than willing -- eager!) to contribute to it. :-)

Sorry, still no ETA on this. We are still evaluating the code and deciding what we want to release. The example we tested was for an internal Phase2 site so it's not yet something we can just release to the community.

+1 following.

I'm looking to migrate a 30-year-old quarterly magazine (issues, articles, author profiles) with accompanying resource library and community discussion from D6/OG to OA2. By the time I'm finished, I suspect I'll have lots of example code to share. But anything that could lower my learning curve / reduce the number of my own mistakes I learn from would be very appreciated.

@dsnopek and @FMB -- how have your sites been progressing? Any examples you can share?

@jakeschlachter: Unfortunately, I haven't started yet. However, I have a client for whom migration of a large number of OA1 sites is entirely unavoidable. So, when this becomes a priority for them, I'll contribute to whatever Open Source migration effort exists or (if necessary!) start such an effort. :-)

jakeschlachter: as a matter of fact I'm (passively) waiting for Phase2's example migration script ;-)

mpotter: what about "release early, release often" (plus a big red sign advising it's alpha software :þ)? You might release the code in a sandbox, if it sounds feasible for you.

Some even pre-alpha migrations samples would be very nice to have as I have to deal with migrating OA case tracker + related content to OA2 work tracker and any help would be welcome (ie. the sample scripts)

I am sure most of us understand your reluctance in releasing something that does not completely work, just stick a 'not ready' notice everywhere. People who are asking for the samples are get it that it will not be perfect and needs to be updated to their specific needs.

I'm going to be experimenting with this next week in order to provide my client with a Statement of Work for future migrations. If nothing else, I'll release the code that comes out of that here! Since this is just the discovery stage, it won't be complete, but it will exist. :-)

FMB: Unfortunately, it is not my decision as to when/if to distribute any migrations scripts, sorry. Don't let this stop people from making their own contributions to this open-source project.

Hi All!

I've started experimenting with migrating sites from OA1 to OA2, using the migrate module (version 2.6-rc1) and migrate_d2d (version 2.1-beta1). I've published my code in a sandbox project here:

https://drupal.org/sandbox/dsnopek/2201363

This mostly proof of concept - it's not complete and would need lots of work to get there! But here is what it does now:

• Migrates Groups -> Spaces along with the Description and Public/Private flag
• Migrates Notebook -> Document page, automatically creating a Section to hold it for each Space

So, first of all the big warning: PLEASE DON'T USE THIS IN PRODUCTION! This is only for other folks looking to experiment and do development for now.

But, if you did want to test it, here is how you'd do that:

1. Install a fresh OA 2.13 site on the same server as your OA 1.x site
2. Install migrate 2.6-rc1 and migrate_d2d 2.1-beta1
3. Clone my oa_migrate module and install it
4. In the settings.php for you OA 2.13 site, add database and files information about your OA 1.x site, for example:
   

   $databases['legacy']['default'] = array(
     'driver' => 'mysql',
     'database' => 'oa1database',
     'username' => 'oa1username',
     'password' => 'oa1password',
     'host' => 'localhost',
     'port' => '3306',
     'prefix' => '',
   );
   
   $conf['legacy_files'] = '/var/aegir/platforms/openatrium-1.7/sites/oa1.example.com/files';
   

5. Run all migrations via the Migrate UI or drush, for example:
   

   drush cc all
   drush mi --all
   

6. Check out your OA 2.13 site and see how the users, Spaces and Notebook content from your OA 1.x site is now present!

If you want to collaborate on extending this code, please open issues with patches in the issue queue for my sandbox project:

https://drupal.org/project/issues/2201363?categories=All

I'm not sure how much time I'll have to continue to work on this in the near future - it depends on how quickly my client would like to move forward with migrating their sites: could be immediately or could be in a couple months! But, I'll commit patches if any come in and if nothing else this could act as an example for other people who want to get started on this. :-)

Please let me know what you think!

Good Morning Everyone!

I'm going to run a migration and see what happens.

@dsnopek I'd like to help! Is there any migration code that needs to be created?

Thank you for starting this!
Jeremy

I am also on the way to make a migration of a large OA1 site. Being able to import groups and notebook, as well as users and mapping them to their groups (now spaces) would actually be enough for my needs. Are there further experiences with the script on #19?

I can also probably allocate a developer for this, helping to further develop the oa_migrate module, *particularly if* @dsnopek would be available to provide some guidance (to a developer without direct Drupal experience)

@gandhiano: I'd be happy to answer any questions in the issue queue on my sandbox module! If you guys come up with any patches, please post them there and I'll review and merge them when I have time. :-) Thanks for the offer to help!

Continue this discussion in the sandbox linked above.

One random note: About a month ago, I helped a client launch their first OA1 -> OA2 migrated site using the code in oa_migrate. So, even though it's incomplete, it works!