Website Migrations
Updated 3 days ago
Assisted migration is included within your plan limits. Once you’ve signed up for hosting, open a ticket in Mi Duplika and tell us what you want to move, which provider you use, and when you’d prefer to make the switch. We’ll confirm what’s included and how to share the necessary access details.
What you can move
Website only. We copy the agreed files and databases, then check the site before pointing the domain to it. You can continue using Google Workspace, Microsoft 365, or another email provider.
Website and email. We coordinate which mailboxes and messages will be moved, the final synchronization, and the change to your email records. See the guide to migrating email to Duplika.
Website with external DNS. You can continue managing DNS through Cloudflare or another provider. We’ll tell you which records to change and which to keep for services that will continue running with another provider.
Migrating your website doesn’t require transferring your domain
You can keep your domain registration with your current provider and host your website with Duplika. The EPP code or Auth Code is used to transfer a registration between companies; it isn’t needed to copy your site’s files and databases. When you sign up for hosting, choose to use your existing domain, and we’ll coordinate which DNS records to change once the destination is ready.
If your website was created on a platform with its own editor, contact us before signing up: we’ll check whether the site can be exported or needs to be rebuilt. Not all platforms can be moved like a WordPress installation.
Migrate it yourself
If your previous provider uses cPanel, you can generate a full account backup. If you’d like our help restoring it, coordinate the migration through a ticket.
Copy your data. If you’re moving everything manually, upload the files using the cPanel File Manager or FTP, and import the databases the site uses.
Prepare your email if that’s moving too. Create the mailboxes at the destination and follow the guide to copying and synchronizing messages. If you’re keeping your provider, retain the email records it uses.
Test your site. Use the temporary access details provided for your account, or follow the guide to edit the hosts file and check your website before changing public DNS. This test only changes what your computer sees.
Update DNS. Make the change in the service that manages your DNS. Update the records for the services being moved, and keep those for external services.
If your site receives orders or changes during the migration
For online stores, learning platforms, and sites with users, an initial copy can become outdated while you continue working. We’ll coordinate the final copy and, when needed, a pause to prevent orders or changes from being split between two servers. The local test doesn’t verify external payment notifications or all integrations by itself; those also need to be checked after the switch.
What to check before canceling your previous service
Check that your website loads over HTTPS, that you can log in to WordPress or your application’s control panel, and that forms or checkout work, if applicable. If you also migrated email, check that the expected messages are at the destination, and test receiving and sending messages with an external account.