Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The safe way to move WordPress posts and pages depends on what you are syncing. Use a full staging-to-live sync only when staging is the complete source of truth and you can account for every change made on production. If the live site has newer posts, comments, users, orders, forms or media, use a selective export/import or another content-only migration instead. In either case, make restorable backups, keep WordPress and the code stack compatible, replace staging URLs with the live URL using a serialization-aware tool, refresh permalinks and caches, and test media and relationships before declaring the release complete.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Choose the right kind of sync first
A staging site is usually a copy of production taken at an earlier point in time. While you work there, the live site may continue receiving editorial and transactional data. Replacing the live database with the staging database can therefore remove legitimate production changes. Decide whether you need an environment release or only a content release before running any migration command.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Decision point | Full staging sync or database replacement | Selective post/page transfer |
|---|---|---|
| What moves | A coordinated set of database data, files and settings supported by the host. A managed WordPress staging service may synchronize media, plugins, themes, posts, pages and menus. | Only chosen posts or pages, with their content and any deliberately migrated media or metadata. |
| Risk to newer live data | High. A database replacement can overwrite live posts, comments, users, orders, submissions and other records created after staging was copied. | Lower because unrelated production data remains in place, although parent pages, custom fields, taxonomies and media still need verification. |
| Best use | A coordinated release in which staging is the source of truth and publishing is paused for the cutover. | A content-only release on an active site, or a situation in which production must keep its newer data. |
| Main work after transfer | URL replacement, permalink refresh, cache clearing and broad functional testing. | Export/import checks, media handling, relationship checks and URL testing. |
Managed WordPress platforms expose their own sync controls and exclusions. The available controls can differ by plan and can change over time, so read the current screen carefully and confirm exactly which database tables and files the operation includes. A self-hosted installation may contain a different database prefix, custom post types, serialized options and host-specific configuration.
Inventory everything that changed on live
Before touching the production database, make a written list of changes made since the staging copy was created. This list determines whether a full replacement is safe and provides a verification checklist if you choose selective transfer.
- Posts and pages published, edited or scheduled on production.
- Comments, registered users and profile changes.
- WooCommerce orders, subscriptions, refunds and customer accounts, if applicable.
- Form submissions, membership records, bookings and other plugin-generated entries.
- Images, documents and other uploads added to the live media library.
- Menus, widgets, navigation relationships and taxonomy changes.
- Plugin, theme, PHP and configuration changes made directly on production.
If any of these records must remain, do not blindly import the entire staging database. Either pause production publishing and use a planned merge, or move only the intended content.
Set a cutover window
For a full replacement, announce a short maintenance window and stop editorial, form and transactional activity before the final backup. If the site cannot be paused, prefer selective transfer and test it on a disposable copy first. Record the start time so you can identify which production records were created during the window.
Free tools Windows power users keep installed
One-click scans. No signup required.
Back up both environments before migration
Keep dated, restorable copies of the staging and live databases. Also copy the uploads directory and any configuration needed to run the site, including wp-config.php values, web-server rules and host-specific settings. Store the backups outside the site being migrated and confirm that the files can be read before proceeding.
A backup is useful only if you know how to restore it. Write down the database name, user, host, table prefix and the location of the uploads directory for each environment. Do not overwrite the only copy when creating a second export. For a high-risk release, take one final live export immediately before the cutover, after publishing has been paused.
Make the two environments compatible
Match WordPress core, active plugins, themes, PHP and relevant configuration as closely as possible before moving data. A database imported into a site with different code can produce missing fields, fatal errors or changed rendering. Activate required plugins on the target before importing content, and check that custom post types and taxonomies used by the staging content exist on live.
Keep staging and production domains clearly separated until the cutover. Never let search engines index the staging domain, and make sure password protection or equivalent access controls do not get copied in a way that locks out the live site.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #2
Option 1: Use a managed full staging sync
On a managed WordPress platform, the full-sync control is appropriate when staging contains the complete release and production changes have been accounted for. Such a sync can include media files, plugins, themes and database content, including posts, pages and menus. The exact inclusions and exclusions depend on the platform and plan.
- Review the platform’s sync summary and identify whether it will replace the production database, copy files, or do both.
- Compare the summary with your inventory of live changes. Stop if the operation would remove records that must be retained.
- Take the final live backup and put the site into the agreed maintenance window.
- Run the sync from staging to production, then wait for the platform to report completion rather than assuming the job finished when the browser returns.
- Open the live site in a private browser session and perform the verification checks described below.
A full sync is not a conflict resolver. If both environments changed the same page, the source environment’s version normally wins. Resolve editorial conflicts before starting rather than trying to reconstruct them afterward.
Option 2: Transfer selected posts or pages
Selective transfer is safer when production has newer content that must stay. WordPress’s built-in Export and Import tools can move a chosen content set; a migration tool can be used when you need more control over custom fields or related data.
Prepare the source export
- On staging, open the WordPress administration area and go to Tools > Export.
- Choose the content type you need, such as Posts or Pages, instead of exporting the entire site.
- Narrow the export by author, date range, status or other available filters so the file contains only the intended release.
- Download the export file and inspect its contents. Confirm that every intended post and page is present before importing it.
Import into production
- Back up production again if the export was prepared earlier.
- In production, open Tools > Import and install or launch the WordPress importer when prompted.
- Upload the export file, map authors deliberately and select the option to download and import file attachments when those attachments should be copied.
- Wait for the importer to finish. Large media libraries can take longer than the content records themselves, so do not close the process after the first page of progress.
- Open representative posts and pages and check parent/child relationships, featured images, inline images, categories, tags and custom fields.
The built-in importer does not automatically solve every dependency. A page that refers to a staging-only menu, shortcode, block pattern, custom post type or plugin field may look incomplete on production even when the post record imported successfully. Install and configure the required code first, then test the rendered page.
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 minuteCommand-line content operations
For repeatable deployments, WP-CLI provides content commands such as wp export, wp import and wp post. Run them from the correct WordPress directory and use the target site’s configuration. Keep the generated export and command output with the release record so you can identify exactly what was moved.
Option 3: Move a complete database manually
A host-neutral full move replaces the target database and then repairs environment-specific values. Use it only after confirming that production records can be replaced or have been separately preserved.
Rank #3
- On staging, export the database with
wp db export backup.sql. Keep the resulting file unchanged as the source backup. - Copy the uploads and any required theme or plugin files to the target, preserving paths and permissions.
- Place the target in maintenance mode and take the final production backup.
- Import the staging database on the target with
wp db import backup.sql. The command reads the target database credentials fromwp-config.php; it does not create the database itself. - Check that the target’s database exists, the credentials are valid and the table prefix expected by the target configuration matches the imported tables.
- Replace staging URLs throughout the relevant tables, then refresh rewrite rules and caches.
Do not edit serialized option values with a plain text editor or an unware search-and-replace script. Serialized strings contain stored lengths; changing a URL without updating the serialization can corrupt options, widgets, page-builder data and other settings.
Replace staging URLs safely
After a database move, links, image references, canonical settings, embeds and plugin options may still point to the staging domain. Use a serialization-aware search-and-replace operation across the required tables. WP-CLI’s documented pattern is:
wp search-replace 'https://staging.example.com' 'https://example.com' --all-tablesSubstitute the real source and destination schemes and hostnames. If the site uses both HTTP and HTTPS, or more than one staging hostname, account for each exact variant. Review the command’s dry-run or report output when available before applying changes. Limit the operation to the intended database when the host contains multiple WordPress installations.
URL replacement does not create redirects or fix external services. Update web-server redirects, CDN settings, password protection, API callback URLs, email links and any third-party integration that explicitly references staging.
Refresh permalinks and caches
WordPress rewrite rules can retain the old environment’s state after a database or domain move. From the target site’s WordPress directory, flush them with:
wp rewrite flushYou can also open Settings > Permalinks and click Save Changes without changing the structure. Clear the WordPress object/page cache, reverse-proxy cache and CDN cache after the URL replacement. WP-CLI’s deployment example includes:
wp cache flushClear caches only after the new files and database are in place. Otherwise, visitors may receive a cached staging page or an old redirect and make a correct migration appear broken.
Verify posts, pages, media and navigation
Use a representative sample rather than checking only the home page. Include newly transferred content, older content, a parent page with children, a post with a featured image and a page containing galleries or downloadable files.
- Confirm the expected posts and pages exist in the administration lists with the correct status, author, publication date and slug.
- Open the public URL for each sample and check that the canonical URL uses production.
- Test parent/child page relationships, menus, breadcrumbs, category and tag archives, pagination and internal links.
- Open featured images, inline images, galleries, PDFs and other attachments. Confirm that files were copied to the correct uploads location and display correctly in the associated content.
- Check block layouts, shortcodes, custom fields and page-builder sections that depend on plugins or themes.
- Search the database or rendered HTML for the staging hostname and investigate every remaining occurrence that should have changed.
- Submit a test form, check email delivery and verify analytics, search and any login-protected area.
For scheduled posts, verify the site’s timezone and cron processing. A staging schedule can publish at an unexpected time when imported into production if the environments use different timezone settings.
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 matchProtect live-generated records during and after the move
Comments, users, orders, form entries and other records created on production are not safely merged by a simple database replacement. If a full push is unavoidable, export or otherwise preserve those records and establish a site-specific merge procedure before the cutover. For stores and membership sites, involve the person responsible for transactions; a missing order or account is more serious than a cosmetic staging difference.
Selective post/page transfer avoids most of this risk, but imported content can still collide with existing slugs, authors, taxonomies or custom-field keys. Resolve duplicate slugs deliberately and confirm that imported authors map to the intended production users rather than creating unintended accounts.
Common failure symptoms and fixes
Images show broken links
Check that attachments were included in the export, that uploads were copied to the expected year/month directories and that file permissions allow the web server to read them. Run the serialization-aware URL replacement again for references still using the staging hostname, then purge caches.
Best Value
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Pages return 404 after migration
Flush rewrite rules with wp rewrite flush or save the permalink settings. Confirm that the web server points to the correct document root and that the page’s slug and parent hierarchy were imported.
The site redirects to staging
Search the database and configuration for the staging domain, including both HTTP and HTTPS forms. Check hard-coded redirect rules, CDN settings, environment variables and plugins that store a site URL separately from WordPress options.
Menus or page-builder layouts are incomplete
Verify that the required theme and plugins are active on production. Some builders store relationships or assets in serialized options and custom tables; use their supported migration procedure rather than editing those values manually.
New live posts or orders disappeared
Stop further writes, preserve the current state and restore the final pre-migration production backup. Do not attempt another import over the damaged database. Reconcile the inventory of production changes, then choose a selective transfer or a controlled merge.
Rollback and post-release monitoring
Keep the pre-migration database and uploads backups until the release has passed its observation period. If critical content, login, checkout or form processing fails, place the site in maintenance mode, restore the database and files, restore the previous configuration, flush caches and test the original URLs before reopening the site.
After a successful release, monitor error logs, scheduled tasks, 404 reports, form notifications, search, redirects and cache/CDN behavior. Keep the staging copy synchronized or rebuild it from the now-current production site before the next release; otherwise the same data-drift problem will recur.
Quick Recap
A practical decision checklist
- Use full sync: staging contains the complete approved release, production publishing can be paused, and every live-generated record has been inventoried and preserved.
- Use selective transfer: production must remain active, or it contains newer posts, pages, orders, comments, users, submissions or media that must not be overwritten.
- Use a custom merge: both environments contain important changes to the same records, or the site relies heavily on commerce, memberships, bookings or custom database tables.
- Regardless of method: back up both environments, match code versions, verify the export, handle media, replace URLs safely, refresh permalinks and caches, and test public URLs before removing the rollback copy.
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.
