As we've mentioned on @opalstack and elsewhere in the forum here we've been building a suite of migration tools to help incoming WF customers move their stuff over to our service.

I'm happy to say that we've deployed the migration stuff across the fleet and the following migrations can be performed automatically!

Wordpress sites (including the app, DB, DB user, and domains)
Generic PHP apps
Generic port listeners (basically anything that listens on a port at WF: Django, Rails, "custom app listening on port", websockets etc)
MySQL databases and users (MariaDB on our side)
PostgreSQL databases and users

The migration tool is wrapped up in a command called wfmigrate.

Here's a quick example of how to use it to migrate a WP site:

Create a shell user via your Opalstack dashboard if you don't have one already: https://help.opalstack.com/article/45/managing-shell-users
Go to https://my.opalstack.com/tokens/ and create a new API token if you don't have one already.
SSH to your Opalstack server as your shell user: https://help.opalstack.com/article/14/ssh-access
Make a copy of our boilerplate config file for the WP migrator (Do this every time to ensure that you're using the latest configuration required by the migrator):
```
cp /opt/app_migrators/wf_wordpress/config-template.ini ./config.ini
```
The other boilerplate config files are located at:
- /opt/app_migrators/wf_generic_php/config-template.ini
- /opt/app_migrators/wf_generic_port/config-template.ini
- /opt/app_migrators/wf_generic_maria/config-template.ini
- /opt/app_migrators/wf_generic_psql/config-template.ini
Edit the config file config.ini that you just created to plug in your Opalstack info and WF info. The options should be fairly self-explanatory and will be fully documented soon, but if you need help just drop a reply here!
Run a simulation to do a pre-migration check. This will ensure that you don't have any conflicting items already created on Opalstack:
```
wfmigrate wordpress ./config.ini --mode simulate
```
You'll see a lot of output go by as wfmigrate inventories all of your items and simulates the migration. There are couple of things to look out for:
- WARNING messages will appear if the simulation encounters an item on your Opalstack server that has the same name as the item on your WebFaction server. Such items will be deleted and replaced when you run the live migration in the next step, so pay attention here! If there's something you don't want to delete, back it up before you run the live migration.
- CRITICAL messages will appear if the simulation runs into a problem that prevents it from performing the migration, like a bad password, a SSH key that can't be set, etc. The simulation will terminate at that point.
Once you've run a successful simulation you can perform the live migration with the do mode option:
```
wfmigrate wordpress ./config.ini --mode do
```
wfmigrate will then run to create all of the necessary items in your Opalstack account and move everything from WF over to our side. All of the above info about WARNING and CRITICAL messages applies to this step as well.

That's pretty much it!

The other items work similarly, and you can run wfmigrate --help to see all available options:

$ wfmigrate --help
usage: wfmigrate [-h] {maria,psql,php,port,wordpress} ...

WF -> Opalstack Migrator

positional arguments:
  {maria,psql,php,port,wordpress}
                        Migration Component
    maria               MariaDB (for MySQL databases)
    psql                PostgreSQL (for PostgreSQL databases)
    php                 Generic PHP
    port                Generic Proxy-Port (custom app listening on port)
    wordpress           Wordpress

optional arguments:
  -h, --help            show this help message and exit

You can also get help on a specific migrator, eg:

$ wfmigrate wordpress --help 
usage: wfmigrate wordpress [-h] --mode {simulate,do}
                           [--loglevel {debug,info,warning,error,critical}]
                           config_path

positional arguments:
  config_path           Path to config.ini

optional arguments:
  -h, --help            show this help message and exit
  --mode {simulate,do}  Mode of operation
  --loglevel {debug,info,warning,error,critical}
                        Logging verbosity level

⚠️ Copy the configuration template every time. We're always updating wfmigrate so you need to have the correct configuration every time you run it.

⚠️ When you migrate a MySQL db from WebFaction, the password for the MariaDB user created on our end will not be the same. You'll need to either change the DB password to match your old one from WF, or update your application settings to use the new DB password. You can find the new DB password in your Opalstack account notifications.

⚠️ The maria migration option does not migrate databases from WebFaction MySQL private instances. It can only migrate MySQL databases hosted on WebFaction's shared MySQL created via WebFaction's dashboard.

⚠️ When you migrate a port listener the migrator will create a matching app on Opalstack and copy the app files over from WebFaction, but the app will almost certainly not work right away. Once the app has been copied you'll need to adjust whatever configuration it uses, for example filesystem paths are different, server IPs, maybe your shell user name, etc. Binaries like Apache and Nginx that are copied over might need to be completely rebuilt from source.

⚠️ READ THE WARNINGS when you run the simulation step. If you see something like "htaccess file contains incompatible directive: SetHandler" or similar then you will need to edit your .htaccess after the migration those directives. If you don't do this then your site visitors will see your site's PHP code instead of the rendered HTML.

⚠️ At this time PostGIS databases cannot be migrated automatically. Instead you'll need to do the following:
1. Export the database at WF and copy the exports to Opalstack.
2. Create new PostgreSQL databases on Opalstack.
3. Contact support to have PostGIS enabled.
4. Import your data.

We'll add more documentation and examples later, and as I said more migrators are coming. The end goal is to have this tool move everything, including all app types and your email as well. It's going to take us a little longer to get there, so in the meantime if you have questions about migrating something over please ask here in the forum or hit up our support address for assistance.