Hmm... looks like migration confuses Postgres. I'll need to manually reset some sequences after migration. Fortunately, that should be easy to do.
I think we need to plan on moving.
The checklist would be like this:
1) Lots of announcing that there will be some downtime and making sure you either know your password or have a valid profile address.
2) Announcing a cut-off time after which posts will not be migrated.
3) In the meantime, I will make sure the new site is ready for migration.
4) After the cut-off time, I can perform the migration and reset postgres sequences.
5.) Once the migration appears successful, announce a shutdown for maintenance. Shut down the new site.
6.) Change the nameservers for the domain over to digital ocean. I don't have the creds to do this.
7.) I can set up DNS on Digital Ocean. Get a certificate. Configure the webserver and application server for the new domain. Then fire it up.
8.) Once the DNS settings propogates when should be in business at [link] (with http redirect to https).
I am very open to a different plan, just putting one out there for a starting point.