Migration Work Flow

• Ensure access to source and target stacks
• Compare target stack for PHP and MySQL versions compatibility
• Determine migration method
  • Is SSH available?
    • Is MySQL dump command available?
    • Is rsync available?
  • For WordPress sites, are backup or migration plugins allowed by the host?
    • We like Duplicator pro
• If available, migrate to staging or test stack first
• Create step by step migration plan
• Execute migration plan at scheduled time
• Test site to confirm migration was successful

Requirements

• Access – at least one method required
  • SSH
  • WordPress Admin with ability to install migration plugin
    • Host must allow migration or backup plugins
• Access to DNS record management
  • We recommend CloudFlare with Proxy enabled for a quick switch over
    • Delegated access via a Member invite is best
• Maintenance page that is to be activated during migration

Downtime Mitigations

We try to make migrations as streamlined and hands off as possible. Downtime during a migration can happen and we try to mitigate this with a variety of methods.

• Migrating sites that are over 10 GB in size via rsync can decrease or eliminate downtime.
• Pointing the source (old) copy to use the target (new) copy’s MySQL database service
  • Requires the firewall on both servers to allow access and the MySQL’s user to allow remote access
• Using Cloudflare with Proxy on or other Full Site CDN services for an “instant” switch over.