Audit + plan + file list
Day 1 · pre-flight
- File list (rsync dry-run) + DB dump size
- Email aliases + DNS records + SSL certs
- Schedule + recovery plan
We move your website, store and email: copy, tests, night-time DNS switch, 301 redirects and Search Console resubmission. All these stages are included in the package price.
Four things you always get with a Balance IT migration package.
Current website audit + migration scope → quote within 24h.
Clone to a staging environment + verification (md5sum). If it differs — it does not go to production.
Cutover at 02:00 (lowest traffic). Low DNS TTL (300s). Recovery plan ready.
Full redirect map (301) + sitemap resubmission in Search Console. SEO preserved.
DNS propagation in 30-60 min, static content in the CDN cache, 301 redirects from the first request. Your customers will not notice the change.
Current website audit (files + DB + email + DNS + SSL)
Clone + staging test (matching hash verification)
Night-time DNS cutover + 301 redirects + Search Console resubmission
File list, DB size, email aliases, DNS records, SSL certificates — before we start.
Clone + verify (md5sum) — bit-for-bit copy. If it differs, it does not go ahead.
Night-time DNS cutover (lowest traffic) + TTL 300s for fast propagation.
Full 301 redirect map + sitemap resubmission + Search Console verification.
Choose the migration scope — always a fixed total price, with post-migration monitoring. Net prices. The amounts shown cover the package scope; additional work requires an agreed scope and confirmed quote.
Delivery 5 days
Delivery 7-10 days
Custom quote
Procedure, tools and quality control — every migration follows the same process, whether for 1 website or multiple sites.
File list (rsync dry-run), DB dump size, email aliases, DNS records (A/MX/TXT/CNAME), SSL certificate status + dates.
File cloning via rsync with verification (--checksum) + DB dump (mysqldump --single-transaction). Bit-for-bit accuracy.
Staging environment setup + clone + verification. md5sum check of every file. If it differs — investigate before cutover.
DNS records updated at 02:00 (lowest traffic). TTL 300s for fast propagation. Recovery plan ready (rollback within 5 min).
Full 301 map (old URL → new URL). Implementation in .htaccess / nginx. Sitemap resubmission + URL inspection in GSC.
Uptime monitoring + Search Console (crawl errors + rankings) + analytics (traffic anomaly detection). 30 days after migration.
We review these questions with you before we confirm the scope and deliverables.
Scope and handover
Which services, accounts and integrations are in scope?
Who handles requests and communicates during an incident?
How do we plan updates, backups and recovery tests?
What support scope and response times go into the agreement?
The Balance IT standard
Pre-flight audit + priority list + schedule.
md5sum verification — if it differs, it does not go to production.
Cutover at 02:00, TTL 300s, recovery plan on standby.
Pre-flight audit + staging test (matching hashes) + night-time cutover + rollback plan. Beyond “hopefully it works”.
Four things that set our migrations apart from “copy, paste and see what happens”.
Every stage ends with a demo and approval. Only then do we move on.
Day 1 · pre-flight
Days 2-3 · verification
Day 4 · 02:00 at night
Week 1+ · post-migration
Loading projects...
People most often call us in one of these situations. If any sound familiar, let's talk.
No vague marketing claims. Clear answers about what moving a website actually involves.