Keep the source active
Do not cancel the existing hosting or email service until cutover, DNS propagation, and final testing are complete.
Service policy
Move eligible websites without a per-site migration fee during your annual plan's onboarding window. Every move remains subject to destination capacity, source compatibility, access, and written scope confirmation.
Effective August 19, 2026
Interactive eligibility check
Answer five short steps for an initial assessment of included website-migration scope, details that require review, and work that is normally quoted separately.
Initial assessment only: this result is not approval or a contractual commitment. Final eligibility, included scope, timing, responsibilities, and any applicable fee must be confirmed by InterProWebHost in writing.
Annual-plan benefit
The benefit applies to new eligible annual hosting plans. Requests must be submitted within 90 calendar days of initial activation and remain subject to source compatibility, valid access, account standing, destination capacity, scheduling, and written scope confirmation.
| Eligible plan | Included website migrations | Capacity boundary | Typical supported sources |
|---|---|---|---|
| Web Hosting | Unlimited eligible websites during onboarding | Must fit the purchased plan's published capacity | cPanel, Plesk, WordPress, and supported portable PHP/MySQL websites |
| Managed WordPress | Unlimited eligible WordPress websites during onboarding | Must fit the purchased plan's website and resource capacity | WordPress installations with supported themes, plugins, and database access |
| NVMe VPS Hosting | Unlimited eligible websites during onboarding | Must fit the purchased VPS and confirmed server configuration | cPanel, Plesk, WordPress, and supported portable website workloads |
| Agency Hosting | Unlimited eligible client websites during onboarding | Must fit the purchased account, website, and resource capacity | cPanel, Plesk, WordPress, and supported portable PHP/MySQL websites |
| Cloud Hosting | Unlimited eligible websites during onboarding | Must fit the purchased cloud plan and confirmed architecture | cPanel, Plesk, WordPress, and supported portable website workloads |
| Dedicated Servers | Unlimited eligible websites during onboarding | Must fit the purchased server and confirmed architecture | cPanel, Plesk, WordPress, and supported portable website workloads |
“Unlimited” removes the standard per-site migration charge; it does not remove plan capacity, fair-use, technical compatibility, security, scheduling, or acceptable-use requirements. Each distinct website is reviewed before acceptance.
Before migration begins
These steps reduce avoidable delays, missing changes, authentication problems, and premature service cancellation.
Do not cancel the existing hosting or email service until cutover, DNS propagation, and final testing are complete.
Maintain a current, separately stored backup of the source environment before any migration work begins.
Avoid changing files, databases, DNS, mail routing, or account settings after the confirmed transfer window begins.
Check storage, mailboxes, databases, applications, and plan limits before approving the destination.
Monitor the approved contact address and be ready to authorize device verification, access, scope, and DNS decisions.
Scope requirements
Migration work begins only after the destination plan is active, required access is available, and both parties have agreed on the source, destination, timing, and expected result.
Migration does not automatically reorganize hosting accounts, redesign websites, upgrade applications, repair corrupted data, remove malware, optimize code, or resolve pre-existing configuration problems. Any such work requires a separate assessment and written scope.
Platform access
Exact requirements are confirmed during assessment. Application-level access alone may not expose the files, databases, mail, DNS, or server configuration needed for a complete transfer.
Hosting-panel access plus FTP/SFTP or SSH, database credentials, and application administrator access. WordPress dashboard access alone may not be sufficient.
Source control-panel URL, username, password, account inventory, and SSH access where available. Full account replication is supported for compatible cPanel-to-cPanel or Plesk-to-Plesk transfers when versions, licensing, permissions, destination configuration, and migration tools permit it. Cross-panel migrations transfer the agreed supported data but do not reproduce every source setting.
Email and mailbox migration is not part of unlimited free website migration. When separately assessed and confirmed in writing, email work may require source and destination credentials, supported IMAP hostnames, a mailbox inventory, DNS access, and platform-specific acceptance testing.
Root or administrative access where applicable, control-panel credentials, firewall access, application inventory, and destination-server access. Custom services, operating-system changes, and unsupported software require assessment.
Registrar or DNS-provider access, current zone records, certificate details, and authorization for the agreed cutover. InterProWebHost prepares and reviews the essential records. The customer makes the final DNS changes or authorizes InterProWebHost in writing to perform them when suitable access is available.
Expected process
The 2–5 business-day estimate begins after access and scope are confirmed. Time spent waiting for credentials, authentication approval, third-party support, DNS decisions, scope clarification, or customer testing is outside that estimate. Large, complex, incomplete, or high-risk requests may take longer.
Identify the source, destination plan, size, services, and preferred timing.
Expect an initial response within 1–2 working days after a complete request.
Approved files, databases, mail, and essential configuration are moved and checked.
DNS changes and final customer testing complete the agreed migration.
Published service standards
These standards apply to eligible migrations within the confirmed scope. They make the review period, synchronization, scheduling, DNS handoff, and specialist services clear before work begins.
The formal review period begins when the migration-completion notice is sent. Report migration-related issues within seven calendar days and keep the source service active through acceptance.
One eligible synchronization of changed website files or databases is included when requested within the review period and the source remains accessible and within the confirmed scope and destination capacity.
A preferred maintenance window may be requested with at least two working days’ notice. The window is not reserved until InterProWebHost confirms it in writing.
Cutovers outside published migration-team operating hours require advance scheduling and a separate written quotation. Standard-hours scheduling remains subject to availability.
Cutover and acceptance
Migration is complete only after the agreed data has been transferred, essential functions have been checked, DNS responsibilities are completed, and the customer has performed final business testing.
InterProWebHost prepares and reviews essential DNS records. The customer makes the final DNS changes or may authorize InterProWebHost in writing to perform them when suitable access is available. DNS propagation is controlled by external networks and may continue after transfer work is complete.
Test the functions that matter to the business promptly after transfer and again after DNS cutover.
Frequently asked questions
Yes, for eligible website moves requested during the first 90 days of a new annual hosting plan. There is no standard per-site migration charge, but every website must fit the destination plan, use a supported source, pass scope review, and comply with this policy. Monthly plans, mailbox moves, unsupported platforms, remediation, custom development, and other excluded work are not included.
InterProWebHost normally responds within 1–2 working days after receiving a complete request. Standard work typically takes 2–5 business days after access and scope are confirmed. Time spent waiting for credentials, authentication approval, third-party responses, DNS decisions, scope clarification, or customer testing is outside the estimate. Data volume and application complexity can also extend the timeline.
The migration plan is designed to reduce disruption, but uninterrupted operation cannot be guaranteed. The source service should remain active and unchanged until cutover and final testing are complete.
No. A compromised, damaged, incompatible, or unsupported source may require remediation or a separate project before it can be migrated safely.
The customer must maintain a current independent backup of the source environment before migration begins. A migration copy is not a substitute for the customer’s backup responsibilities.
Not as part of unlimited free website migration. Supported data is transferred substantially as it exists at the source. Reorganization, redesign, application upgrades, malware removal, data repair, performance optimization, and correction of pre-existing configuration issues require a separate assessment and written scope.
No. Unlimited free migration covers eligible websites, not mailbox data or email-platform configuration. Email messages, calendars, contacts, aliases, forwarders, shared mailboxes, authentication records, devices, and third-party platform configuration require a separate assessment and written scope.
InterProWebHost prepares and reviews the essential records. The customer makes the final DNS changes or may authorize InterProWebHost in writing to perform them when suitable access is available. External DNS propagation can continue after the transfer itself is complete.
No. Keep the source hosting and email services active until the agreed data has been verified, DNS propagation is complete, and final business-function testing has passed.
Yes. One standard delta synchronization of eligible changed website files or databases is included when requested within the seven-calendar-day review period. The source must remain active and accessible, and the work must stay within the confirmed scope and destination capacity. Further synchronizations or unsupported data require a separate assessment.
The formal review period is seven calendar days from the migration-completion notice. Report migration-related issues during that period and keep the source service active until validation, DNS propagation, and acceptance are complete.
Yes. Request a preferred window with at least two working days’ notice. The window is subject to staff and platform availability and is not reserved until InterProWebHost confirms it in writing.
No. A cutover outside published migration-team operating hours requires advance scheduling and a separate written quotation.
Full account replication is supported for compatible cPanel-to-cPanel or Plesk-to-Plesk transfers when versions, licensing, permissions, destination configuration, and migration tools allow it. Cross-panel migrations transfer only the agreed supported data and do not reproduce every source setting.
Share your current provider, platform, data size, number of sites or mailboxes, access method, and preferred timing. A specialist will confirm eligibility, scope, and any applicable fee.