Website and server migration to cp.lv
We build a full copy, verify it by IP address and switch DNS last — visitors normally see no downtime
A correct migration looks like this: first a full copy of the project is brought up on the new server, then it is verified by IP address — pages open, the database answers, mail goes out — and only after that is DNS switched over. The old server keeps running while the records propagate. Because of that order visitors normally do not notice the move at all: they land either on the old copy or on the new one, but never on an error page.
What gets moved
Website files, databases, web server and mail configurations, cron jobs and SSL certificates.
What we need from you
Access to the current server or a fresh backup, access to the domain DNS, and a list of the services that must work after the move.
How long it takes
It depends on the data volume: a typical site with a database takes a few hours, a large project with a big database takes longer. We give a firm estimate once we see the sizes.
The order of work
Four steps, and DNS always comes last.
We look at what is being moved
We map out the inventory: sites, databases, mail, background jobs. At this point the configuration of the new server is chosen to match the current load.
We bring up the copy
The environment is deployed on the new server and the data is transferred. The old server keeps serving visitors throughout.
We verify it by IP
The copy is opened directly by IP address and checked end to end: pages, forms, database, mail, scheduler.
We switch DNS
The domain records are changed. While they propagate, both servers run in parallel, so no requests are lost.
We size the new server to your real load
A migration is a good moment to stop overpaying. We look at how loaded your current server really is and pick a plan to match those numbers: if 8 vCPU and 8 GB RAM at €10.99/mo is enough, that is what we will say instead of pushing a bigger plan.
You can verify the new configuration before paying: VPS and cloud servers come with a 5-hour test period, and deploying a copy of the project on it is exactly what it is for.
VPS plans
Moving from a specific provider?
Most projects reach us from Hetzner, Contabo, DigitalOcean and AWS. We match an equivalent configuration by vCPU, RAM and disk so that performance does not drop after the move — the price and specification comparison is on a separate page.
If a contractor used to run the server and the credentials are gone, that is solvable too: the migration can start from a backup or from an export in the control panel.
Compare providersQuestions about migration
Did not find your answer?
Write to us via the contact page form.
Not with the correct order of work. The copy is prepared and verified in advance, DNS is switched last, and the old server stays online while records propagate.
Support help with moving onto our server is part of the service. If the work is heavy — for example untangling an unusual configuration — we offer an administration package and name the price in advance.
Access to the current server or a fresh backup, access to the domain DNS, and a list of what must work afterwards: sites, mail, cron jobs, integrations.
Mailboxes and settings are moved when mail lives on the server itself. If it is with an external provider, only the DNS records change and the mailboxes stay where they are.
We migrate from a backup or from an export made in the control panel. A migration with no data at all is impossible — we need at least a copy of the files and the database.
A typical site with a database takes a few hours including verification. A large project with a big database takes longer: most of the time goes on copying and checking, not on configuration.
Yes, that is what the 5-hour test period on VPS and cloud servers is for: deploy the copy, measure speed and compatibility, and only then decide about payment.
A Let's Encrypt certificate is issued on the new server right after DNS is switched. A paid certificate is transferred together with its private key if you still have it.