Your migration shows completed — great. Before you switch DNS, spend five minutes verifying the new copy. Because your old site is still serving visitors, you have all the time you need to check without any pressure.
1. Load the migrated site
Preview your site on iWebVault before changing DNS — ask our team for the preview method for your setup, or add a temporary entry to your computer’s hosts file pointing your domain at the new server IP. Click through your key pages.
2. Check the database-driven parts
If you run WordPress or any database app, log into its admin area and confirm posts, products, settings, and users are all present. Because database names are preserved, this normally just works.
3. Confirm email accounts
In your new cPanel, open the Email Accounts section and confirm your mailboxes are listed. If you keep email on iWebVault, you’ll point MX records here during cutover.
4. Verify files and uploads
- Spot-check that images and media load
- Confirm any upload folders are present
- Check that addon domains and subdomains exist
5. Review cron jobs
Open the Cron Jobs section and confirm your scheduled tasks came across with the right timing.
Why verify before cutover, not after
The whole point of checking while your old site is still live is that you have unlimited time and zero risk. If you wait until after DNS cutover to look, any problem is now affecting real visitors. Verifying first means you catch gaps calmly and fix them before anyone is impacted.
A practical preview method
The simplest way to view your migrated site before cutover is a hosts-file entry on your own computer, mapping your domain to the new iWebVault server IP. Only your machine sees the new server; everyone else still uses your old host. Our team will give you the IP and the exact line to add. With that in place you can browse your whole site on iWebVault as if it were live.
Deeper checks for dynamic sites
- Log into your CMS admin and confirm you can edit content
- Submit a test form and confirm it processes
- For stores, view a product, add to cart, and reach checkout
- Confirm scheduled tasks (crons) are listed with correct timing
- Check that any file uploads directory is present and writable
Email verification
Open Email Accounts in your new cPanel and confirm each mailbox exists. If you’ll host email on iWebVault, you’ll set MX records to point here during cutover; if you use external email, you’ll preserve those MX records instead. Either way, confirm the mailbox list looks right now.
If you find something missing
Don’t switch DNS and don’t cancel anything. Your old site is untouched and live. Note exactly what’s missing — a database, a folder, an email account — and open a ticket. We can re-pull that piece or re-run the migration before you cut over, with no impact to your live site.
Building a verification habit
Treat post-migration verification as a fixed routine rather than an optional extra. The same short sequence works every time: load the site, exercise the dynamic features, confirm email accounts, spot-check files and uploads, and review cron jobs. Running this checklist while the old site is still live means any gap is found in a no-pressure environment and fixed before it ever touches a real visitor.
What a good verification looks like for a WordPress site
- Open the site’s front page via your preview method and click through the menu
- Log into wp-admin and confirm posts, pages, and media are present
- Check a few images load, confirming the uploads folder migrated
- If you run a store, view a product and reach the checkout step
- Open the plugins list to confirm everything’s intact
Verification for non-WordPress sites
The principle is the same whatever your stack: load the site, test the parts that touch the database, and confirm anything that writes to disk (uploads, caches, logs) is working. A static site needs only a click-through; a custom application needs you to log in and exercise its core functions. Tailor the depth to how dynamic your site is.
Recording what you checked
For an important site, jot down what you verified — front page, admin login, a form submission, email accounts present. If a question arises after cutover, you’ll know exactly what was confirmed beforehand. For a reseller moving client sites, a short per-site verification note is professional and reassuring evidence that each move was checked.
The discipline that makes it safe
The entire zero-downtime promise rests on one discipline: verify before you switch, never after. It’s tempting to switch DNS the moment the status reads completed, but those few minutes of verification are what guarantee your visitors never see a broken site. Build the habit and migrations become routine rather than risky.
Key takeaways
Verify before you switch, never after. While your old site is still live, load the migrated copy via a preview method, exercise the database-driven features, confirm email accounts, spot-check files and uploads, and review cron jobs. Catching a gap now is trivial; catching it after cutover means it briefly affected real visitors. Only switch DNS once these checks pass.
What’s the easiest way to preview before cutover?
A hosts-file entry on your own computer mapping your domain to the new iWebVault IP — only your machine sees the new server while everyone else still uses the old host. Our team will give you the IP and the exact line to add, letting you browse the whole migrated site safely before any switch.
What’s next
Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.
Was this helpful?
Thanks for your feedback!
