You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/migrate-wordpress.md
+15-10Lines changed: 15 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom: seodec18
12
12
---
13
13
# WordPress Migration to Linux App Service
14
14
15
-
This articles describes two ways to migrate WordPress from App Service on Windows or external hosting providers to App Service on Linux.
15
+
This article describes two ways to migrate WordPress from App Service on Windows or external hosting providers to App Service on Linux.
16
16
17
17
>**Note:** First migrate the content to a test instance, validate all scenarios, and if everything works as expected, swap this instance to the production slot.
18
18
@@ -38,10 +38,10 @@ By default, the file upload size for WordPress on Linux App Services is limited
38
38
39
39
### Export the data at source site
40
40
41
-
1. Launch WordPress Admin page
42
-
1. Open All-In-One WP Migration plugin
43
-
1. Click on 'Export' option and specify the export type as file
44
-
1.This bundles the contents of database, media files, plugins, and themes into a single file, which can then be downloaded.
41
+
1. Launch WordPress Admin page.
42
+
1. Open All-In-One WP Migration plugin.
43
+
1. Click on 'Export' option and specify the export type as file.
44
+
1.Download the bundle.
45
45
46
46
### Import the data at destination site
47
47
@@ -59,7 +59,9 @@ The prerequisite is that the WordPress on Linux Azure App Service must have been
59
59
60
60
### Manually Export the data at source site
61
61
62
-
>**NOTE:** Depending on the size of your content and your internet connection, this operation could take sometime.
62
+
> [!NOTE]
63
+
> Depending on the size of your content and your internet connection, this operation could take several minutes.
64
+
>
63
65
64
66
1. Download the **wp-content** folder from the source site. You can use popular FTP tools like [FileZilla](https://filezilla-project.org/download.php?type=client) to connect to the web server and download the content.
65
67
@@ -80,11 +82,14 @@ The prerequisite is that the WordPress on Linux Azure App Service must have been
80
82
81
83
4. Upload the new contents of **wp-content** folder using the File Manager. Click on the label that says '**Drag a File/Folder here to upload, or click to select one**'.
82
84
83
-
5. You can either point your WordPress to [use an existing MySQL database](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/using_an_existing_mysql_database.md), or use the steps below to migrate the content to the new database server (an Azure Database for MySQL flexible server) created by the WordPress on Linux App Services offering.
85
+
5. You can either [use an existing MySQL database](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/using_an_existing_mysql_database.md) or migrate the content to a new Azure MySQL Flexible Server created by App Service on Linux.
84
86
85
-
>**NOTE:** Azure Database for MySQL - Single Server is on the road to retirement by 16 September 2024. If your existing MySQL database is hosted on Azure Database for MySQL - Single Server, consider migrating to Azure Database for MySQL - Flexible Server using the following steps, or using [Azure Database Migration Service (DMS)](/mysql/single-server/whats-happening-to-mysql-single-server#migrate-from-single-server-to-flexible-server).
86
87
87
-
6. If you chose to migrate the database, import the SQL file downloaded from the source database into the database of your newly created WordPress site. You can do it via the PhpMyAdmin dashboard available at **\<sitename\>.azurewebsites.net/phpmyadmin**. Please note that if you are unable to one single large SQL file, please try to break it into multiple smaller parts and try uploading. Steps to import the database through phpmyadmin are described [here](https://docs.phpmyadmin.net/en/latest/import_export.html#import).
88
+
> [!NOTE]
89
+
> Azure Database for MySQL - Single Server is on the road to retirement by 16 September 2024. If your existing MySQL database is hosted on Azure Database for MySQL - Single Server, consider migrating to Azure Database for MySQL - Flexible Server using the following steps, or using [Azure Database Migration Service (DMS)](/mysql/single-server/whats-happening-to-mysql-single-server#migrate-from-single-server-to-flexible-server).
90
+
>
91
+
92
+
6. If you migrate the database, import the SQL file downloaded from the source database into the database of your newly created WordPress site. You can do it via the PhpMyAdmin dashboard available at **\<sitename\>.azurewebsites.net/phpmyadmin**. If you're unable to one single large SQL file, separate the files into parts and try uploading again. Steps to import the database through phpmyadmin are described [here](https://docs.phpmyadmin.net/en/latest/import_export.html#import).
88
93
89
94
7. Launch the Azure Portal and navigate to your **App Service -> Configuration** blade. Update the database name in the **Application Settings** of App Service and save it. This will restart your App and the new changes will get reflected. [Learn more: WordPress Application Settings](https://github.com/Azure/wordpress-linux-appservice/blob/main/WordPress/wordpress_application_settings.md)
90
95
@@ -101,7 +106,7 @@ The prerequisite is that the WordPress on Linux Azure App Service must have been
101
106
102
107
### Install Recommended Plugins
103
108
104
-
It's an optional step, after the site migration it is recommended to validate that you have the default recommended/equivalent plugins activated and configured accurate as before. If you are prohibited from not configuring them as per your organization governing policies, then you can uninstall the plugins.
109
+
It's an optional step, after the site migration it is recommended to validate that you have the default recommended/equivalent plugins activated and configured accurate as before. If you're prohibited from not configuring them as per your organization governing policies, then you can uninstall the plugins.
105
110
106
111
- The W3TC plugin should be activated and configured properly to use the local Redis cache server and Azure CDN/Blob Storage (if it was configured to use them originally). For more information on how to configure these, refer to the following documentations:
0 commit comments