Migration process¶

Migration of your website to a new server is a rather complicated procedure and should be done by professionals. Here is the scenario we follow, working together with the client we can make the migration as smooth as possible.

Migration process and milestones¶

1. Estimation We examine your current server and environment and estimate the time needed for website(s) migration. (CRONs, database size, store size, third-party integrations and dependencies).
2. New server configuration. We create an optimized server configured specially for your project.
3. Pilot migration We make a copy of your project on the new server, run functionality tests and monitor the website performance amending the configuration until it works perfectly well. If there are any server-related issues, they are fixed during this period with no extra fee.
4. DNS change DNS records are changed to the new ones and it takes up to 24 hours to update them. Within these hours we proxy the traffic to your current server through the new one.
5. Final migration We stop proxying the traffic to the old server, close the storefront(s), synchronize the database and files and open the storefront(s) again. The period of time when the storefront is closed depends on the type of access you provide us with and the size of the database (if we get SSH, the final migration takes 2-5 minutes).
6. Access information We send you the email containing new access credentials and detailed information about our services and how we provide them. Read more here.

Migration is complete. Your website is now on and is monitored 24/7. You are guaranteed 99.99% server uptime with expert technical support. Our DevOps team is ready to help if something goes wrong with the server.

Access needed for migration¶

SSH access is the best for migration. It allows estimating and performing migration fast and minimum downtime.

FTP is much slower and may cause some downtime (closed storefront) in case there is a big number of images and the store size is large.

If you have WHM/cPanel/Plesk/etc., give us access to it and we will try to find the optimal solution.