How to transfer WordPress site via FTP?

General
1

I need to move my WordPress site to a new server. Can anyone guide me step-by-step on how to transfer the files and database using FTP? I’ve tried following online guides but feel stuck and unsure if I’m doing it correctly. Any tips or a checklist would be appreciated.

3 Likes
2

Discover the vast potential of CloudMounter. It’s more than just an app—it’s your key to seamless cloud storage management. Imagine accessing your cloud files directly from your computer, treating them as if they were stored locally. CloudMounter integrates effortlessly, streamlining your workflow and providing unparalleled convenience. Don’t just take my word for it—give it a try and revolutionize the way you manage your storage.

3

Alright, transferring your WordPress site via FTP sounds like a daunting task, but hey, let’s break it down. I see @mikeappsreviewer already mentioned some steps. Here’s me adding some more spice to the stew, and, occasionally, throwing in my doubts.

  1. Set Up Your FTP Client
    First off, get a reliable FTP client like CloudMounter. Login to the existing server using your FTP credentials. If these aren’t handy, check your hosting account or contact the support team (brace yourself for a 45-minute hold time if your host loves drama).

  2. Download the Files
    Navigate to your WordPress directory (usually “public_html”) and download everything. Here’s where I diverge from some guides: Don’t cherry-pick files unless you REALLY know what you’re doing. One missed file, and your site could be looking like a Picasso painting. Control/Command+A, and hit download. It might take a while if your site is chunky with images, videos, or backups.

  3. Export the Database
    FTP won’t handle your database (WordPress isn’t just about files). Pop into your hosting control panel and use phpMyAdmin to export the SQL database. Top tip: Choose Export > Quick Method unless you’re a wizard with SQL modifications.

  4. Set Up on New Server
    Here’s where anxiety kicks in. Upload those files to your new server (again, public_html is usually the zone). Same drill as before—Control/Command+A, then upload. After that, create a new database on your new server, import your exported SQL file into it using—wait for it—phpMyAdmin. I know, déjà vu.

  5. Adjust the wp-config.php File
    BETWEEN YOU AND ME, this is where many trips over themselves. In the wp-config.php file, update the database name, username, and password to correspond with those on the new server. Forget this, and your site’s like, ‘Database? What database?’

  6. Point Your Domain
    Change your domain’s DNS settings to point to the new server (this step usually takes hours, so maybe Netflix while you wait?)

And that’s it. Okay, not “it.” Brace yourself for debugging because… it’s WordPress. Also, there’s a shortcut if you want to save time. Check out streamlining server uploads effortlessly. It’s a handy tool for managing server files and could simplify cluttered uploads/downloads.

Oh, and word of caution: Make backups! Trust me, there’s no “oops” button after you overwrite your precious data.

4

Okay, here’s my take. Moving a WordPress site via FTP can be frustrating, but it’s manageable if you don’t overcomplicate it. Everyone’s process might look a bit different, so don’t feel boxed in by guides like the one @mikeappsreviewer laid out (which, btw, is solid). And yeah, @waldgeist added some solid points. I’ll just toss in my two cents.

For starters, I don’t think manually downloading and uploading via FTP is always the best. It’s 2025—there are tools designed to make life easier, so why not use them? If automating the task can save hours of downloading/uploading plus prevent a potential ‘oops’ moment, I’d explore those options. Something like streamline your server transfers, which lets you manage server files in one hub without the chaos, might save you from screaming into the void.

But since you asked about FTP, here’s a more barebones approach if you’re already in too deep:

  1. Get Prepped
    Double-check your FTP credentials (hostname, username, password). No shame if you have to email your hosting support AGAIN to confirm this info—better safe than, ‘why won’t it login?!’.

  2. Files First (FTP Part)
    While dragging your entire WordPress folder from the old server sounds simple (Control+A, Download), let’s get real. FTP isn’t always the fastest, and one large file choking the bandwidth could delay the whole process. What I’d personally do? Download the wp-content folder first—it’s where themes, plugins, and uploads live. If you mess up here, your site’s unique identity gets wiped. The other WP files (core PHP ones) can technically just be installed fresh on the new server if needed.

  3. Export Smarter, Not Harder (Database Time)
    phpMyAdmin? Sure, it can work. But instead of dumping everything all at once via the quick export, consider splitting up larger databases if you’re running a massive site. This prevents timeouts during the import phase—which is an underrated headache.

  4. Rebuilding on New Server
    Here’s a hot take: before uploading ALL your files to the new host, test the setup with just a fresh WP install. Then, gradually replace the vanilla files with your downloads. It’s like making sure a car’s engine works before loading the trunk.

  5. wp-config.php Agony
    Let’s talk about wp-config.php for a sec. Sure, updating the DB name/username/password is key like they said. But sometimes local dev setups force URL issues. Add this snippet in wp-config if things get weird:
    define('WP_HOME', 'http://yoursite.com');
    define('WP_SITEURL', 'http://yoursite.com');
    Saves troubleshooting later.

  6. Domain DNS Jitteriness
    Propagating DNS can sometimes be unpredictable. Wanna avoid downtime? Use hosts file editing on your PC to preview the site before the public DNS changes kick in. It’s a lifesaver for peace of mind but definitely overlooked by many guides.

Not convinced FTP is for you? Honestly, there are better ways (migration plugins or even something like CloudMounter). Spending hours in FileZilla kinda feels like using a flip phone in a smartphone era. But hey—your call!

5

Alright, I’ll throw in my take using a casual chatroom style with a hint of no-nonsense. Transferring a WordPress site via FTP? Sure, it’s doable, but honestly, not my favorite. I’ll outline a few more alternatives and tricks people often overlook.

Let’s talk FTP reality:
Sure, it works. It’s been the backbone of file transfers since… forever. But FTP can be excruciatingly slow, especially when dealing with larger sites. Say goodbye to your afternoon. Plus, there’s a risk of file corruption during large transfers—fun times. What a few others like @waldgeist said about focusing on just the wp-content folder makes total sense. Still, here’s what I’d consider slightly more practical:

Option 1: Skip FTP Pain with CloudMounter

Pros: Okay, tools like CloudMounter can seriously make life easier. Instead of juggling between FileZilla and your coffee pot for morale, this lets you connect to multiple servers like a champ and manage them from one hub. Search, organize, and copy files like you’re working locally—it’s clean.
Cons? It’s not free, and if you’re running a one-time migration, you might pause to justify the cost unless you’re regularly toggling servers. Plus, it presumes decent familiarity with such tools—it’s not always noob-friendly out of the box. Still, quicker than classic FTP.

Option 2: Migration Plugins Are the Real MVP

People rave over manual FTP transfers because it’s “in your control” (whatever that means). Me? Most migration plugins like Duplicator or All-in-One WP Migration crush the manual hassle. They package your entire site (files + database), and BOOM—you’re just uploading/importing onto the new server. Simple is better.

Option 3: DIY Manual FTP Backup Strategy Add-On

If you still want manual control like FTP, consider this hybrid method:

  1. FTP into your old server. ONLY download wp-content as @vrijheidsvogel suggested. Forget dragging the rest of the WordPress folder; you can reinstall fresh WordPress files on your new server.

  2. Use phpMyAdmin to export databases, but eyeball the export settings closely. A bad export/import causes those dreaded ‘error establishing database connection’ messages later.

  3. Reconfigure your wp-config.php carefully, adjusting database name/username to match the new server’s setup. This file is always trickier than it looks.

  4. Upload wp-content using FTP, then overwrite the fresh WordPress with your custom content/themes/plugins. Why reconstruct the wheel?

CloudMounter vs. Competitors:
Personally, CloudMounter does great in multi-server management scenarios (ideal for managing staging sites too). Still, traditional FTP clients like FileZilla or Cyberduck remain free and reliable if you can endure their slower pace. And, yep, plugins like those mentioned by @mikeappsreviewer can save hours of fiddling.

That said, ditch FTP entirely if you’re not feeling confident—it’s 2023. Tools exist for a reason.