On the target server, install WordPress if it is not already installed. Make a copy of the database file you just downloaded. On your working server, go to the phpMyAdmin (MySQL), locate the database used by the working WordPress web site, make a back-up file of it, and download the backup to your computer. Step 4.Ĭreate a backup of the working site’s database. Make a copy of the wp-content folder you just downloaded. Once in the new location, you will return s to their original settings (Step 10).Ĭreate a back-up of the working site’s content folder. Use an FTP client and download the wp-content folder to your computer. Turn off custom s. In the WP dashboard on the working server, go to Settings>s and select the default button. Several of my colleagues use CyberDuck or FileZilla. FTP client: the application you use to access the back door of a web site on your server.Target server: the server you’re moving the web site to (its permanent home).Working server: this is where you developed the web site (the sandbox).I’ve included links to my key resources at the end of the article. From that research I developed a which resulted in a successful, glitch-free migration. This process does not make use of plugins and avoids the need to edit the database.īefore I moved a WordPress web site for the very first time, I prepared for the move by doing a lot research, culling information from the WordPress Codex and elsewhere. Here is my step-by-step process for migrating a WordPress web site from a working or development server (sandbox) to its permanent server.

Filezilla vs cyberduck vs fetch 2016