What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
You can move a website without taking it offline by copying it to the new host first and changing public DNS only after the copy passes private testing. Keep the old account serving visitors, lower the web-record TTL 24–48 hours before cutover, synchronize the final database changes for dynamic sites, then switch only the A, AAAA or CNAME records. Leave the old host running while DNS caches expire and keep a tested rollback ready.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What “without downtime” really means
A hosting transfer does not instantly move every visitor from one server to another. Recursive DNS resolvers cache the old address until its TTL expires, so some visitors may reach the old host while others reach the new one. The safest design is therefore overlap: both copies work during propagation, and neither server is taken offline during the switch.
As an Amazon Associate I earn from qualifying purchases.
There is no universal guarantee that every resolver will update at the same moment. A migration is operationally successful when the old site continues serving requests, the new copy is tested before exposure, writes are synchronized, and you can revert DNS quickly if a critical fault appears.
Migration timeline at a glance
| Stage | When | Purpose |
|---|---|---|
| Inventory and backup | Before provisioning | Record the stack and create a verified rollback copy. |
| Provision destination | Several days before cutover | Build the account, runtime, database, SSL and application settings without changing public DNS. |
| Lower web DNS TTL | Ideally 24–48 hours before cutover | Encourage resolvers to discard the old web address sooner. |
| Copy and test | Before cutover | Transfer files and database, then test through a hosts-file mapping or private preview. |
| Final synchronization | Immediately before DNS change | Capture orders, comments, uploads and other writes made since the first copy. |
| DNS switch and monitoring | After tests pass | Change only web records, watch both versions and validate from multiple networks. |
| Retirement | After a safety period | Archive the old account and cancel it only after traffic, mail and integrations are stable. |
1. Inventory everything before touching DNS
Make a written inventory of the current environment. This prevents a technically correct file copy from omitting a dependency that visitors or administrators rely on.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
- List every domain, subdomain, parked domain and alias, including both the apex name and
wwwhostname. - Record the PHP or other runtime version, database engine and version, required extensions, web-server rules and document root.
- Document cron jobs, scheduled workers, queue consumers and any server-side scripts that run outside normal page requests.
- Export the current DNS zone or copy each record into a change sheet. Separate web records (A, AAAA and CNAME) from mail records (MX, SPF, DKIM and DMARC), verification TXT records and service-specific entries.
- Note the active TLS certificates, HTTP-to-HTTPS redirects, HSTS behavior, CDN settings, cache rules and firewall allowlists.
- List plugins, themes, custom code, external APIs, payment callbacks, webhooks, analytics, search tools, contact forms and transactional email providers.
- Confirm that you can access the registrar, DNS provider, old host, new host, database and backup storage before scheduling the move.
Take screenshots or save configuration exports where a setting is difficult to reproduce. The inventory becomes your acceptance checklist after the cutover.
2. Create and verify a rollback backup
Download the complete site, not only the public pages. For a WordPress installation this includes the WordPress directory, uploads and images, plugins, themes, configuration files and a full database export. Other applications need the equivalent source files, user uploads, environment configuration and database dump.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Store the archive somewhere independent of both hosting accounts, such as offline storage or a separate controlled location.
- Verify that the archive opens, that the database dump can be read, and that important uploads are present. A backup that has never been tested is not a rollback plan.
- Record the database name, user, password, host and table prefix separately so you can rebuild the application if the destination fails.
- Keep the pre-migration backup unchanged. Create a second archive after the final synchronization if the site receives ongoing writes.
Do not cancel the old plan or delete its files as part of the first transfer. The old, known-good copy is your fastest recovery option.
3. Provision the new host without changing public DNS
Create the destination account and configure its web root, database, database user, runtime version, required extensions, rewrite rules, file permissions, caching and SSL. Use a temporary provider address or private preview while the real domain still points to the old server. UpdraftPlus migration guidance likewise recommends setting up the new hosting space before changing DNS.
Match versions deliberately. A newer PHP release, changed database collation, missing image library or different rewrite module can break an application even when every file copied correctly. If you must change versions, test that change separately from the hosting move whenever possible.
Issue or validate the TLS certificate on the new host before cutover. Prepare certificates for both the apex domain and www if both are used. Confirm that the certificate chain, HTTPS redirect and any HSTS policy behave correctly on the private copy.
4. Lower the DNS TTL before the move
TTL is the period a recursive resolver may retain a DNS answer. Lower the TTL for the web A, AAAA or CNAME records at least 24–48 hours before the planned switch so caches can learn the shorter value while the old server is still live.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
| Value or timing | How to use it | Qualification |
|---|---|---|
| 300 seconds | A common temporary target for the web records during migration. | HostPanel migration guidance, 2026. |
| 86,400 seconds | An example of a 24-hour default TTL that may delay a cutover. | SiteGround Academy guidance, 2026. |
| 24–48 hours ahead | Time to allow resolvers to refresh after lowering the TTL. | Use this window when the DNS provider and schedule allow it. |
Lower the TTL only for records you intend to switch. Leave mail and unrelated service records alone unless they are deliberately moving. After the migration is stable, restore a production-appropriate TTL; keeping an unusually short value increases DNS query traffic and does not improve application performance.
5. Transfer the files and database
Choose a method that matches the site’s risk and your ability to verify it. Copy uploads and configuration as well as application code, preserve permissions, and recreate scheduled tasks on the destination.
| Method | Best fit | Strengths | Risks or checks |
|---|---|---|---|
| Manual files plus database export | Administrators comfortable with SFTP, rsync and SQL. | Maximum control over exactly what is copied and when. | Requires careful permissions, configuration, database import and final-sync work. |
| Migration or backup plugin | Typical WordPress sites. | Packages files and database and can simplify restore-based moves. | Check storage limits, serialized data handling, plugin compatibility and private testing. |
| Managed migration | High-write stores, multisite networks, fragile legacy systems or owners without a verified backup. | Specialist help with consistency, DNS and rollback. | Confirm exactly what the service covers, including email, DNS records, integrations and the final synchronization. |
For a manual move, export the database from the old host, upload the files by SFTP or rsync, import the dump into the new database, and set ownership and permissions appropriate to the new web server. Do not copy transient cache directories as if they were authoritative content unless the application requires them.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteIf the public domain and paths remain identical, keep the application’s public URL settings unchanged. In WordPress, that generally means copying the files and database and changing only the database credentials in wp-config.php when the destination uses different values.
6. WordPress-specific decisions
When the domain and URLs stay the same
WordPress documentation states that a move to another server does not require reinstalling WordPress. When the database and URL remain the same, copy the files and database, then update the database host, name, user and password in wp-config.php if necessary. Leave the home and siteurl values unchanged; a server change alone is not a reason to run a broad search-and-replace.
When the domain or path changes
Update the WordPress URL settings and use a search-and-replace method that understands serialized data. A naïve text replacement can change string lengths inside serialized values and corrupt options, widget settings or metadata. Take a database backup immediately before any URL rewrite and test the replacement on the private copy.
Permalinks and scheduled work
Confirm that the destination has the correct rewrite rules. After the move, open the WordPress Permalinks settings and save them if the server’s rewrite configuration differs, then test representative posts, pages, feeds and attachment URLs. Recreate cron jobs and check whether the site uses real server cron or WordPress’s request-triggered scheduling.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
7. Test the new copy privately
Never make the new server public for the first time by changing DNS. Map the real hostname to the new server’s IP in a local hosts file, or use the provider’s private preview. This lets you test the production hostname, certificate and redirects while ordinary visitors still reach the old host.
- Find the destination server IP and the exact hostname you intend to test.
- Add a temporary hosts-file entry that maps that hostname to the new IP. On Windows the file is typically
C:WindowsSystem32driversetchosts; on macOS and Linux it is typically/etc/hosts. - Open the site in a private browser window and test the apex and
wwwnames, using HTTPS. - Remove the temporary entry after testing, or keep it only while performing the final verification. Do not leave a stale override in place when diagnosing post-cutover DNS.
Run a written acceptance test rather than checking only the home page:
- Open representative posts, pages, category archives, media files, feeds and search results.
- Sign in to the administration area, create a test draft and confirm that permissions and uploads work.
- Submit contact forms, newsletter forms, login flows, checkout and other conversion paths in a safe test mode.
- Check redirects, canonical URLs, robots directives, sitemap generation, HTTPS, mixed-content warnings and error logs.
- Trigger a scheduled task, webhook and external API callback where possible, and verify that firewall or allowlist rules permit the new IP.
- Confirm analytics, search-console verification and transactional email behavior without changing the live DNS records.
8. Synchronize writes on dynamic sites
A static brochure site can often tolerate a simple final copy. A store, forum, membership site, booking system or comment-enabled publication cannot: orders, comments, registrations and uploads may arrive while the initial database is being exported.
Choose one of two controls before cutover. Either schedule a brief maintenance window that prevents writes while you take the final export, or use a migration process that synchronizes changes from the old database to the new one. Announce the window to staff, stop background workers that could create new records, complete the final database import, and verify the newest transaction or comment on the destination before switching DNS.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep the old site available for reads during propagation, but do not allow two independent application copies to accept writes indefinitely. If both servers process orders or account changes, reconciling divergent data becomes substantially harder than a short, planned write freeze.
9. Change only the web DNS records
After private tests pass and the final synchronization is complete, edit the DNS zone. Change the A and/or AAAA records, or the web CNAME, to the new provider. Do not replace the entire zone with a template from the new host unless you have compared every record.
MX, SPF, DKIM, DMARC, verification TXT records and unrelated service records may still belong to your existing mail or third-party providers. A careless DNS change can leave the website working while mail delivery fails silently. Copy those records exactly when they are staying in place, and move them separately only when you have a deliberate email migration plan.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Record the old values before saving the change. That gives you a precise rollback instruction instead of relying on memory during an incident.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →10. Monitor propagation and validate the live site
Some visitors will continue reaching the old server until their resolver’s cached answer expires. Check the domain from more than one network, such as a mobile connection and a separate broadband connection, and inspect DNS answers from multiple geographic locations if available.
- Watch uptime checks, web-server access logs, application logs and error rates on both hosts.
- Submit forms and test a real transaction path in a controlled manner. Confirm that email arrives and that callbacks or webhooks are acknowledged.
- Check certificate validity, redirect chains, CDN behavior, cache headers and HSTS on both apex and
wwwhostnames. - Compare analytics and search-console signals for missing traffic, indexing errors or a sudden increase in server errors.
- Confirm that backups now run on the new host and that scheduled jobs execute at the expected times.
Do not interpret the first successful browser test as complete propagation. Continue monitoring while cached DNS entries age out.
11. Keep a rollback path
Leave the old hosting account active during propagation and for a safety period after the switch. Namecheap recommends keeping the old plan for at least three days. The exact period should reflect your traffic, publishing schedule, transaction volume and contractual renewal date.
If a critical fault appears, restore the recorded A, AAAA or CNAME values for the old server. Keep the new copy intact while diagnosing the problem, and avoid making unrelated changes during the incident. For a dynamic site, decide what happens to writes received on either host during rollback; a DNS reversal does not merge databases automatically.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCommon rollback triggers include missing orders or comments, broken authentication, failed payment callbacks, widespread 5xx errors, invalid certificates, inaccessible media or mail records accidentally changed during the cutover.
12. Close the old account only after confirmation
When traffic, email, integrations, backups, SSL renewal and monitoring are stable, take a final archive of the migrated site and its configuration. Check that you have exported any logs or invoices needed for compliance, and document the new DNS values and administrator credentials in your normal secure system.
Best Value
Only then cancel the old hosting account. Removing it earlier destroys your easiest rollback and can turn a recoverable configuration mistake into an outage.
Troubleshooting the most common transfer failures
The new site shows a database connection error
Recheck the destination database host, name, user, password and permissions in the application configuration. Confirm that the database import completed and that the destination runtime can reach the database server. Do not change public DNS again until the private copy loads reliably.
Recommended Free Tools
Pages work but pretty URLs return 404
Compare rewrite rules and web-server modules with the old host. For WordPress, save the Permalinks settings after confirming the destination rewrite configuration. Test both a post URL and an administrative request before cutover.
Visitors see mixed content or certificate warnings
Validate certificates for every hostname, check HTTP-to-HTTPS redirects and inspect hard-coded asset URLs. If a CDN or proxy terminates TLS, verify its origin certificate and the new origin IP as well.
Email stopped after the website move
Compare MX, SPF, DKIM, DMARC and verification TXT records with the pre-migration export. Restore the mail records if they were overwritten, and test both inbound and outbound delivery. Website DNS and email DNS are related but are not the same migration.
Only some users report the old site
This is normally DNS propagation, not proof that the new server is broken. Check both hosts’ logs, verify the reduced TTL was published before the switch, and continue monitoring until cached answers expire. Keep the old server available during this period.
Choosing the safest approach for your site
Manual transfer is appropriate when you understand SFTP or rsync, SQL exports, permissions and DNS. A WordPress migration plugin reduces repetitive work for a conventional installation, but you still need a verified backup, private testing and a plan for serialized data and dynamic writes. Managed assistance is sensible for high-write commerce, multisite networks, legacy applications or any migration where you cannot independently restore the backup.
Whichever method you select, judge it by five practical questions: Can it preserve data during the final sync? Can you test under the real hostname before DNS changes? Does it provide a clear rollback? Does it handle application-specific data such as serialized WordPress values? Does someone own the DNS, email and third-party integration checks? The method is less important than maintaining the copy-first, switch-last sequence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




