How to migrate to Verpex
Moving an existing site to Verpex — what they handle for you, what you'll do yourself, and the safe order to do it in.
Pre-Migration: Verify the Basics
Check your current site’s resource usage against Verpex’s Bronze plan limits: 20GB storage. No control panel is specified in the data pack, so assume migration will involve manual file transfers or standard tools like cPanel if your current host uses it.
Lower DNS TTL Early
Verpex has 10 global datacenters (New York, London, Singapore, etc.). If uptime consistency matters (100% over 30/90/365 days per the data), prioritize the location closest to your audience. Reduce your DNS TTL to 300 seconds at least 24 hours before migration to minimize downtime during cutover.
Move Files and Test
No "free migration" is mentioned in the data pack, so plan to:
- Back up your site’s files and database manually.
- Upload to Verpex via FTP/SFTP (no panel specified).
- Test functionality using the temporary URL Verpex provides (standard for shared hosting). Verify TTFB (137ms desktop) and fully loaded time (636ms desktop) match your expectations.
Final Cutover and Support
Switch DNS records only after confirming the test site works. Verpex offers 24/7 live chat and ticket support if issues arise post-migration. Their 45-day money-back guarantee (data pack) provides a buffer if performance doesn’t meet claims.
Effort level: Moderate. No automated migration tool is indicated, so manual work is likely unless your current host uses cPanel.