Job hosting-custom-php-site-off-cpanel · revised 9 October 2026
Move a custom PHP site and its database off shared cPanel hosting
Move your custom PHP site's files and MySQL database to a managed host, test the pages and forms on a preview address, then switch traffic with a way back.
You might be seeing
- The old host's renewal price is suddenly much higher
- The site goes offline when several people use it
- The old developer still holds the hosting account
- Your host has given you a deadline to move
No passwords, keys, card details or admin invites needed to start.
What usually happened
The website's PHP files, database, uploads, scheduled tasks and mail settings live together in an old shared hosting account. Copying only the files leaves the database or user uploads behind, while flipping DNS too early sends visitors to an untested copy and can lose form submissions.
Who it’s for: Owner of a small business whose custom PHP site has outgrown shared cPanel hosting or whose original developer's hosting account is closing.
Usually starts when: The host raises prices, gives notice, or the site slows down or repeatedly goes offline, and you need to leave without losing enquiries or records.
The result: Your custom PHP site runs at the new managed host, every agreed page and form works on a preview copy, existing records and uploads are present, and the domain points to the new site after a client-approved switch.
Check whether this job fits
Five questions, about two minutes. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Check the current PHP version and backup size
In cPanel, look under MultiPHP Manager or PHP Selector for the version, then Backup for the full backup size.
Look for: A PHP version the new host supports, and a backup smaller than 10 GB. Ask the new host about anything else before paying for a plan.
What you get
- A move inventory of files, database, uploads, PHP version, scheduled tasks and mail senders
- Test results from the preview site for the pages and forms you agreed
- The database sync record and the switch and switch-back steps
- Before and after DNS and live-site checks
Included
- One custom PHP site with one MySQL database, up to 10 GB of files and a database up to 2 GB
- Files, uploads, database and required PHP extensions copied to the new managed host you choose
- Configuration adapted to the new host without changing business features
- Preview-site tests of agreed pages, logins and forms, and a final sync of database and uploads, with old-site writes paused until old DNS answers expire
- A switch and switch-back plan for the domain holder, with live checks after the change
- A cutover window long enough to keep writes blocked at the old host until its cached DNS answers stop reaching it; if this is not acceptable, a separate replication plan is needed
Not included
- WordPress and other CMS sites, or Laravel apps with multiple worker services
- Buying or managing the new host account for you
- Moving business mailboxes to a new email provider
- Rewriting old PHP code to work on a newer version, beyond minor configuration changes
- Ongoing hosting administration or security monitoring
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
On the preview address, each agreed page and form works, the login accepts a test user, and the PHP error log shows no new fatal error
Evidence: Screenshots, form confirmation and a redacted error-log excerpt
The destination database has the same table counts and the newest agreed test record as the source after the final sync
Evidence: Before and after row-count and newest-record comparison
After the domain holder switches DNS, the public site loads over https, an agreed form reaches the inbox, and MX records still point to the same mail provider
Evidence: Status checks, test enquiry and public DNS lookup
After the final sync, the destination has the newest agreed database record and uploaded file, while the old site’s write paths remain blocked until its DNS cache window ends
Evidence: Timestamped before/after record and file hashes, old-site maintenance screenshot and DNS TTL notes
Sign-off. You sign off only after the old-site write block has held through the DNS cache window, the destination has the newest agreed record and upload, and live page, form and mail-DNS checks pass. The old host stays available for 14 days.
If it fails. If the agreed live checks fail, you do not pay. We help your domain holder restore the old routing, keep both hosts safe while DNS caches settle, and reconcile any new records or uploads before writes resume. You keep the preview-site findings.
When it fits, and when we stop
It fits when
- You own the site and have a full file and database backup, or the old host will give you one
- The new host supports the PHP version and extensions your site needs, or the site is already tested on its PHP version
- You or a trusted holder can create the new hosting account and change the domain's DNS
- You can name the pages and forms that must work, and can agree a short pause on writes for the final sync
- You can keep the old host running through the DNS cache window, with its forms and other writes blocked after the final sync
- If old mailboxes are on the departing host, you have a confirmed continuing mail plan or a separately completed mailbox move
We stop and tell you if
- No safe backup of the old site's files and database is available
- The site takes card numbers directly or stores regulated data that needs a specialised migration route
- The new host cannot run a library, PHP version or database the site needs and no small compatibility fix exists
- There can be no pause on new writes and records must never be lost: that needs a live replication plan quoted separately
- Bookings or orders cannot be paused while old DNS answers remain cached, and no separately agreed replication plan exists
- The old host will close mailboxes before email is moved or confirmed to stay active elsewhere
What could go wrong
The old host stays up at least 14 days and has a snapshot from before the final sync. If live checks fail, the domain holder restores routing but cached DNS may still reach either host; keep both safe and reconcile any destination records and uploads before allowing writes again.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| New form entries are written to the old site during the final copy | We agree a short write pause, do a final sync, and verify the newest records before switching. |
| The new host lacks a PHP extension or has a different database version | We compare versions and extensions before restoring; an incompatible host is a stop, not a production surprise. |
| The DNS switch changes MX records and stops email | Only the website address records change; the reviewer compares MX, SPF and DKIM before and after. |
| A rollback loses records that arrived at the new site | We keep an export of new records and reconcile them before pointing traffic back. |
A second reviewer checks database consistency, mail DNS records, the write-pause plan and the switch-back steps before the switch is approved.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Inventory the old site's files, uploads, database, PHP extensions, cron tasks and email settings
- Restore a copy at the new host on a preview address without changing live DNS
- Run the agreed page, form and login tests and fix host-specific configuration
- At cutover, block writes on the old site, take a final database and uploads sync, then verify the newest record and file on the preview site
- Independent review of the test results and switch and switch-back steps
- Your domain holder switches traffic; keep old-site writes blocked until cached DNS answers expire, then check the live site, database and mail DNS
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Hosting, platform and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
After the move, discuss scheduled page, form and backup checks with separately agreed alert handling.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Ask the new host whether its team will migrate the site at no extra charge; many managed hosts do. Check that they include database and email records in that promise.
- If the old host is otherwise working and only the renewal price changed, ask for its retention price before paying for a move.
Questions
Will my website or email go down?
We test before switching and leave mail DNS untouched. Forms, bookings or orders on the old site must pause while DNS caches expire; we agree that window in advance. If you cannot pause them, this fixed move is not the right plan.
Do you choose the new host for me?
We can check that a host you name supports your site's PHP and MySQL requirements. You buy and own the account; some hosts will move the site for free.
What if something breaks after the switch?
The old host stays running for at least 14 days. Your domain holder can point traffic back, after we account for any new form entries.
Does this include our business email?
This moves the site only. Mail can stay at the old host only if the provider confirms it will keep running after the website leaves. If that host is closing, move the mailboxes first.
Start with an email
Send us
- Your site's address and the names of the old and proposed new hosts
- The current PHP and MySQL versions if your control panel shows them
- Approximate size of the site backup and database, if known
- The pages and forms that matter to the business
- Whether logins, uploads, bookings or orders change the database during the day
Later, once you agree
- A full backup of site files and database, shared through a client-controlled route
- A test environment at the new host and a non-production test login if the site has logins
- An authorised domain holder available to apply the switch and switch-back steps
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You open and keep the new hosting account and domain. AI agents prepare the move on a preview site with scoped access after intake; a separate reviewer checks the cutover plan. You or your holder approve the final DNS switch and keep the old host running for rollback. Synthetic Industry is owned by a person and remains accountable for the agreed work.
Or write to hello@syntheticindustry.ai with “hosting-custom-php-site-off-cpanel” as the subject.