Migrate an existing site or organisation

Migrate an existing site or organisation Organic Design procedure

This article or section is a stub. Stubs are articles that have not yet received substantial attention from the authors. They are short or insufficient pieces of information and require additions to further increase the article's usefulness. The project values stubs as useful first steps toward complete articles. See Wiki workflow and Wikipedia:Stub for more details on this process. See all the stubs in Category:Stubs

The plan is to set up a procedure that builds the new organisation from the current set up. This should include a content migration mechanism. The client can then see the final result of the intended migration and ensure that the result is complete and functional. Some aspects will require manual repair which in some cases is best left until the actual process has taken place, all such items should be noted and listed beforehand.

Create ontology

All of the current environment needs to be coherently mapped so that the migration process doesn't miss anything out.

Test migration

This phase involves running through the migration workflow and making the result available under a test domain. The post-migration work can then be established and problems fed back into the migration workflow ready for the next test iteration.

Actual migration

When the test environment and post-migration manual workload is acceptable to the admin members:

• the current site is locked to read-only
• the content migration is run so that the target is current
• the post-migration manual workflow is run through by the necessary roles
• the domain is moved over

See also

• Set up a new organisation