This project is not covered by Drupal’s security advisory policy.
An experimental module for migrating Open Atrium 1.x sites to Open Atrium 2.x.
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:
- Install a fresh OA 2.x site (tested to work with OA 2.13) on the same server as your OA 1.x site
- Clone my oa_migrate module:
git clone --branch 7.x-2.x http://git.drupal.org/project/oa_migrate.git cd oa_migrate - Install migrate 2.x-dev, migrate_d2d 2.x-dev and apply this patch #1834016: Add support for migrating node revisions. Or you can just use the
oa_migrate.makefile provided:
drush make --no-core oa_migrate.make drush en -y migrate migrate_d2d - Install the oa_migrate module:
drush en -y oa_migrate - In the settings.php for you OA 2.x 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['oa_migrate_register_migrations'] = array( 'legacy' => array( 'name' => 'OA1 -> OA2 migration for legacy site', 'database' => 'legacy', 'files_path' => '/var/aegir/platforms/openatrium-1.7/sites/default/files/', ), ); - Run all migrations via the Migrate UI or drush, for example:
drush cc all drush mi --all - Check out your OA 2.x 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:
Project information
- Project categories: Content editing experience, Import and export, Developer tools
- Created by dsnopek on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
