[Resolved] Migrating our site from staging to production
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is planning to migrate their staging site to production and has questions regarding the completeness of their migration checklist, the necessity of including WPML in the migration, updating WPML plugins, and managing site registrations. Solution: 1. The migration checklist is complete, but the client should use an additional tool like WPML's built-in import/export feature. More details can be found here: WPML Export and Import documentation. 2. There is no need to include WPML in the migration if the client is only importing products/pages, provided WPML is already configured on the production site. 3. The staging site URL will not be automatically removed from the client's account; the client needs to manually remove it. 4. The production site URL will not be automatically added; the client needs to manually register it. 5. The client should update WPML Multilingual CMS and WPML String Translation on the staging site before migration to ensure compatibility and functionality. This can be done via Plugins > Add New > Commercial > Check for updates. 6. If content is being migrated via WPML Import/Export and not by pushing the complete website to production, the client will need to connect and share translation memory between the sites. This step can be executed at any point before deleting the staging site, ideally before opening a page with the WPML Translation Editor. More information on this process can be found here: Automatic Translation Subscription for Multiple Sites. 7. During the migration process, the client should select "Yes / This is only a copy - original site is still running" to preserve the staging site and share translation memory with the production site.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am planning to migrate our staging site, hidden link, to production, hidden link. We have created a checklist for the migration and highlighted WPML-related steps. We are following documentation related to WPML and site migration.
Symptoms:
Not applicable.
Questions:
1. Can you please confirm that our migration checklist is complete? The checklist can be accessed via the following link: hidden link
2. Should we include the WPML plugin when we perform the migration, since it will already be installed on the production site when the migration begins? See row 11 of the Google sheet.
3. Once the migration is complete, will our staging site URL be removed from our list of registered sites?
4. Once the migration is complete, will our production site URL be added to our list of registered sites?
5. Our registered sites list indicates that neither WPML Multilingual CMS nor WPML String translation are up to date. Do you recommend we update WPML Multilingual CMS and WPML String translation before the migration?
6. If you recommend making the updates, can you make them for us?
7. If you are unable to make the updates for us, can you please provide us with documentation on how to carry them out?
Question 1 from our ticket:
—
You mentioned we would need to use WP import / export or WP All Import. Is this the “WP import / export” plugin you are referring to?
Question 2 from our ticket:
—
Since there’s no need to include WPML in the migration how do we exclude it from our migration?
Question 6/7 from our ticket:
—
I don’t see a “Commercial” tab in the plugins section of my site, so I am planning on installing/updating the plugins manually. Would you suggest downloading and using the OTGS Installer (V 3.1.10) or would you suggest downloading the WPML components for manual installation? We would be updating WPML Multilingual CMS from v 4.7.1 to v 4.72 and the String Translation plugin from v 3.3.1 to v 3.3.2.
Please keep in mind that we want to preserve our current WPML settings and completed translations.
Item 8 from WPML support team response
—
If you are migrating content via WPM Import export and not by pushing your complete website to production, then you will need to connect and share translation memory between them:
- https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/.
At what point in the migration process should this be executed?
Question 9 (new question)
—
We would like to preserve our staging site and have it connected to and share translation memory with our production site. Based on that which option should we select during the migration process:
“Yes / This is only a copy - original site is still running” or "No / I changed the address of the site to this new one”?
The staging site we are migrating should appear where our current blog is displayed, KingCountyMetro.blog.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
You had mentioned that your live site already had WPML installed which is why my colleague said it was not needed to reinstall it again.
However you now mention you need to install it again? I'm not sure how you're migrating at this point but the plugins on your staging site need to be in the live site as well.
You can install them manually at this point via the OTGS Installer. The settings and configuration remain on the database so if you're not doing a database migration, then you have to do everything manually and reconfigure everything, manually.
The step to connect the sites can be done at any moment, I suggest you do it before you try to open a page with the WPML Translation editor. You need to have both sites available at that moment (live and staging), so it needs to be done before you delete the staging site.
You should select the "yes" option and on the se ond screen you'll see instructions to connect the sites (staging and live).
Please allow me to clarify: We don't intend to install it on the staging site again, however, it was recommended that we update WPML to the latest version on the staging site before migrating and that we install it on the production site prior to the migration. Can you please confirm that this is correct?
At the moment, we have installed WPML on the staging site, but not on production. We intend to migrate everything over, including all blog posts and media library. The only elements of the production site we want to preserve are the subscriber database and JetPack settings.
We have already translated a few blog posts on the staging site, so when we migrate we will need all WPML configuration settings and in-language posts to migrate over as well.
Based on this, I have two questions:
1. Can you please tell me how to update our WPML-related plugins on the staging site without overwriting any of the configurations we set up or deleting any of the in-language blog posts we have produced?
2. Below is a link to a Google doc we prepared for the migration. Can you please confirm that all of the steps I have listed that involve WPML (highlighted in yellow) are correct and in the right order? Please let me know if anything should be added or removed.
I'm dropping in to follow up on my previous message. As previously noted, we do not intend to install WPML on the staging site again, however, it was recommended that we update WPML to the latest version on the staging site before migrating.
At the moment, we have installed WPML on the staging site, but not on production. We intend to migrate everything over, including all blog posts and media library. The only elements of the production site we want to preserve are the subscriber database and JetPack settings.
We have already translated a few blog posts on the staging site, so when we migrate we will need all WPML configuration settings and in-language posts to migrate over as well.
Based on this, I have two questions:
1. Is there anything WPML-related that we need to install on the production site before the migration?
2. Can you please tell me how to update our WPML-related plugins on the staging site without overwriting any of the configurations we set up, or deleting any of the in-language blog posts we have produced?
3. I updated the existing checklist and produced a second checklist just in case we choose to migrate our site using UpDraft Plus. Can you please confirm that we covered everything WPML-related (highlighted in yellow)? Please note any steps that should be added or deleted.
Metro Matters Migration - WordPress Migration method: hidden link
Metro Matters Migration - UpDraft Plus (free plugin) method: hidden link
Before answering anymore of your questions, to clear things up, can you please first let us know what kind of migration method are going to use.
Are you going to migrate only WPML related things from staging to production via Import/export methods explained in WPML docs, or are you going to push database from one website to another, or something other?
Then I will answer any questions you may have, since approach in different method is different.
1) If you are using some 3rd party plugin to migrate / push one website / database from one URL to another (staging to production), then this plugin should push all the same and will overwrite you current instance, so there is no point to setup beforehand, anything on your production website.
2) If you want to only migrate WPML content then, you can use WPML Import export method and only export/import related content from one WPML website to another WPML website.
We will be using a 3rd party plugin to migrate/push one website/database from one URL to another (staging to production). The only things we would like to preserve/restore from the original site are our JetPack (including newsletter) settings and subscriber database.
We plan to use either WordPress.com's native migration tool or UpDraft Plus. I have provided steps for using each method in the Google Sheets linked below. Can you please confirm that we covered everything WPML-related (highlighted in yellow)? Please pass along any steps that should be added or deleted.
Metro Matters Migration - WordPress Migration method: hidden link
Metro Matters Migration - UpDraft Plus (free plugin) method: hidden link
A few additional questions:
1. We would like to update our WPML-related plugins on the staging site without overwriting any of the configurations, string translations, taxonomy translations, in-language blog posts, etc. Would you suggest using the OTGS installer or, would you suggest updating each plugin separately?
I am not aware what is WordPress method, but looks like same approach of migration database / content from one website to another.
Basically, in this way, there is no difference to WPML part. If you are migrating the database from one website to another, WPML content settings will also be moved. You will then get a banner asking you if you have moved website, that you need to follow and confirm, re-register with new key since it is a new URL, and that is it, from the WPML side.
Yes, the checkboxes look good.
1) You can not use OTGS installer since that is first-time installer plugin. Go to Plugins > Add New > Commercial > Click “Check for updates" and update WPML plugins to the latest versions.
Please make sure to create a backup before doing any actions, just in case.
Thank you for clarifying. Below is a link that explains how to sync between staging and production sites. We do plan to overwrite the database.
hidden link
1) Regarding the plugin updates - I do not see a "Commercial" tab in my admin area, nor am I able to locate the plugins via search. Is it okay to download the plugins from https://wpml.org/account/downloads and upload them to our site while maintaining all of our configurations and translations?
