Platform.sh Project Migration

This utility allows very ealsy to transfer project from one Platform.sh instance/region to another and change organization.

Requirements

1. You need to have installed Platform.sh CLI
2. You need to have "admin" access to both Platform.sh projects (current one, and the one where you want to migrate your project)
3. Both Platform.sh projects should have the same resources (disk/CPU). Otherwise, it might be impossible to sync some mounts/start some services on the new Platform.sh project.
4. If your project has multiple domains, it is a good idea to make them CNAME of your internal DNS record. And point your internal DNS record to Platform.sh. It will make DNS switching step much simpler. Example:

domain1.com  =>
domain2.com  =>
domain3.com  => <project>.ccplatform.net => <platform.sh edge_hostname> 
....         =>
domainX.com  =>

Usages

You can migrate your project from one Platform.sh instance to another (including multiple environments), just by running this command:

./migrate.sh

Then answer questions to define:

• Which project ID you want to migrate
• On which region do you want to migrate
• In which organization do you want this new project to be part of
• Which app (multi-application project) contains database (use app if single application)
• your Github API Token

Alternatively, you can run all those steps manually:

1. Setup Platform.sh project IDs (please ignore prompts to redeploy the project):

   ./steps/set_projects.sh <FROM_PROJECT_ID> <TO_PROJECT_ID>

2. Copy project title, users, variables and setup deploy key:

   ./steps/copy_project.sh

3. For each environment you need to: copy it, update its settings, copy environment variables and copy GIT branches:

   ./steps/copy_environment.sh main
   ./steps/copy_environment.sh stage

4. Sync data (mounts, DB) for an environment:

   ./steps/copy_data.sh main app
   ./steps/copy_data.sh stage app

note: please provide environment (main | stage) and service (app) having the database relationship.

5. Remove all assigned domains from old project and assign them to new one:

   ./steps/project/transfer_domains.sh

   Script will ask you to point project domains to edge host of new Platform.sh instance. You can do this later, but in this case, additional manual redeploy will be required to update SSL certificates.

At any point you can sync additional environments manually:

./steps/copy_environment.sh feature1
./steps/copy_data.sh feature1 app
./steps/copy_environment.sh feature2
./steps/copy_data.sh feature2 app

note: For `copy_data.sh script`` please provide environment (feature1 | feature2) and service (app) having the database relationship.

Manual actions

Please note, this script will ask to make some manual actions:

1. Setup new deployment SSH key
2. Set correct value for sensitive project/environment variables (as it is impossible to get those values using Paltform.sh CLI)
3. Point project domains to new edge_hostname

But there are some other things you need to set up manually, and there will be no prompt for them in the script:

1. Integration for Github is done, for other integrations on the new project, please setup it manually (health notifications/web hooks/etc)
2. Setup non admin users
3. Update HTTP access control settings (most likely for non production environments)
4. Copy persistent data for additional services (Solr/Elasticsearch/etc)

[comment]: <> FHK: done as i add a new parameter to the copy_data.sh script to define which service contains the db, and then, platform db:dump do the trick to retrieve the corresponding relationship [comment]: <> (4. Script takes care only about database database relation. If you are using another name for it (or have multiple database relations) you need to tune [copy_db.sh](https://gitlab.com/contextualcode/project-migration-platform.sh/blob/master/steps/environment/data/copy_db.sh&#41;)