How Migrations Work
Migrating a Magento store from another server to Stratus can be complicated for many without the necessary experience or skills. MageMojo provides an initial, free migration service for new clients. The MageMojo migration service moves your current store to MageMojo and helps with configurations to make sure it is ready to launch.
NOTE: migrations take some time to complete. MageMojo assigns migrations to our migration specialists. Due to the complexity and data integrity requirements of migrations, we cannot accommodate rush requests for migrations.
After MageMojo provisions a new server, an email is sent to the store owner requesting information needed for the migration task:
- Domain(s) to be migrated
- Path to files on current host (e.g. /var/www or /home/username/www)
- Control Panel URL
- Control Panel Username
- Control Panel Password
- SSH URL
- SSH Username
- SSH Password
- DNS Registrar URL
- DNS Registrar Username
- DNS Registrar Password
Depending on the current hosting, store owners may not have immediate access to all the needed information. The owner should consult with their original developers or the hosting provider asssistance.
At a minimum, MageMojo Support needs SSH access to dump the store database and sync the site files between the servers. Alternatively — but much less desirable — MageMojo can use a pre-made archive. Many control panels, such as cPanel can create such archives.
For stores who elect to not use the MageMojo DNS system, DNS Registrar credentials are not needed.
Once MageMojo support has verified access to the current server, the migration team will:
- Dump the existing database(s) to a file
- Sync the files and database dump to the new MageMojo server
- Copy any SSL certificates that can be accessed
- Copy any extra frameworks/databases detected such as WordPress blogs
- Setup and import the database at MageMojo
- Configure the vhost
- Set the base URLs to a temporary domain (typically the MageMojo server hostname) or the server IP
- Confirm the site loads
- Review the site for performance
- Review the site for malware (PHP backdoors etc)
- Review the site for missing patches and security updates
Internally, MageMojo also conducts a second review after a technician completes the initial migration. The second tech checks that everything above was completed correctly and nothing was missed.
After confirming the site appears to be working as expected, MageMojo will request testing by the store owner with a link to the migrated site and separate emails detailing the initial server setup and migration instructions.
Review and Testing
The purpose of the review period is to make sure everything you need is working for your store. The site should be tested as it would normally be used. Changes should be made in the Magento admin and any business critical custom scripts or cron tasks tested.
During testing, the checkout process will likely produce an SSL Error. This behavior is normal during this phase and is a result of using an unsecure URL during testing.
During the review and tesing, MageMojo recommends the following minimum testing actions be completed:
Check categories, product pages, and search results.
Add a product to the shopping cart.
Verify coupons and special pricing rules.
Verify the Magento Admin login process.
Check for any Magento extensions that require licenses. Make sure extensions are functioning and do not need an updated license.
Login to the Stratus Control Panel.
Make sure all crons are listed in the Crons Panel.
View add-on domains and/or subdomains in MHM control panel. Make sure any that were setup on the previous host have been added.
Once the review and testing is accepted and confirmed by the store owner, MageMojo Support will request a time for the final switchover. During this final step, the support team will:
- Set maintenance mode on the previous Magento site to prevent orders
- Resync the database with a fresh copy from the previous host
- Clear the site cache on the new MageMojo Magento store
- Update the nameservers
The site will then appear live, but due to DNS propagation, this may not be immediate.
NOTE: It is recommended to schedule the final migration for a low traffic/off-hours time to minimize impact to your customers.