• Resolved dlmsontag

    (@dlmsontag)


    I’m working on a manual migration from the staging site to production. I am very comfortable working with databases and plan to export all the tables, make my changes and create a new production table set (after renaming the existing production tables).

    In the instructions found at Migrate WordPress Staging Site to Production Site ? WP STAGING (wp-staging.com), step 3.1 outlines performing a search/replace of //mysite.com/staging to //mysite.com on the staging tables and set wpstg_is_staging_site to false. Straight forward so far.

    I notice in the SQL file I exported, I see there are also references to the staging site folder using the server path of /home/servername/public_html/stagingfolder/…

    Should these references be changed to remove the staging folder or am I just overthinking this and getting into too much detail? My gut reaction is to update and remove all references to the staging site/folder. However, if they are not changed, will there be any negative impact when that staging folder is deleted?

    Thanks in advance for assistance!

Viewing 1 replies (of 1 total)
  • Plugin Contributor Fayyaz

    (@fayyazfayzi)

    Hi @dlmsontag,

    The staging site references should be updated with the new production site’s directory path. The manual migration is a multi-step and technical process. We only recommend this to highly skilled and technical users.

    The PRO version performs automatic search and replace to ensure accurate directory, data, and table mapping.

    Cheers

    Fayyaz

Viewing 1 replies (of 1 total)
  • The topic ‘Manual migration of DB tables search/replace server name?’ is closed to new replies.