Copy files and database, change configuration and test under a temporary method before moving public DNS.
Applies to: WordPress on Tudor Internet Web Hosting
WordPress problems often come from the interaction between PHP, plugins, themes, caching, scheduled tasks and database state. Change one item at a time, record what you changed and keep a known-good backup before updates or repairs.
Before you start
- Sign in to the Customer Portal and open the affected hosting service.
- Take a current backup before changing website files, databases, DNS or application configuration.
Step-by-step
- Inventory the source PHP version, plugins, theme, database size, scheduled tasks, email dependencies and current DNS TTL.
- Export the database consistently and copy all WordPress files, including hidden files and uploads.
- Create the destination database and user, import the data and update wp-config.php with the exact destination credentials.
- When the hostname changes, replace URLs using a serialisation-safe WordPress tool rather than a plain SQL text replacement.
- Test the destination using a hosts-file method or temporary hostname without changing public DNS.
- Freeze or synchronise content at cutover, update DNS and monitor both old and new logs while caches expire.
- Keep the source intact until forms, login, media, scheduled tasks, HTTPS and email notifications have been verified on the destination.
Confirm the result
- The intended hostname loads over HTTPS from a private browser session and serves the correct website.
- Forms, database-driven pages and the administration area work without a new PHP, permission or redirect error.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The restored site opens but behaves incorrectly. | Files and database were restored from different times, cached data is stale or configuration still points to the old location. | Align the restore points, clear application caches and verify URLs, credentials and scheduled tasks before declaring recovery complete. |
| Recent data is missing. | The selected recovery point predates the change or the data was stored outside the backed-up location. | Stop making further changes, identify the required timestamp and ask support what recovery points remain available. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Prepare a site for migration
- Test a migrated website before DNS cutover
- Export a database backup
- Connect using FTP over TLS (FTPS)
- Diagnose a WordPress database connection error
Last reviewed: 2026-07-18.
