PHP fix. Our sites are patchedWhat to do
TopSyde
Abstract artwork of dark topographic contours crossed by faint gold pathways

WP Engine Alternatives for Agencies Moving 40 Client Sites

WP Engine alternatives for agencies: what pooled plans cost against per-site hosting, how to stagger a 40-site move, and keep DNS, email and SSL working.

Rachel Nguyen

Rachel Nguyen

Senior WordPress Engineer

··15 min read

Last updated: November 21, 2026

The best WP Engine alternatives for agencies are the ones that match how you bill clients. If you charge per client, per-site managed hosting turns hosting into a line item each client pays for. If you absorb hosting yourself, a pooled plan looks cheaper on paper. Either way, move the 40 sites in staggered waves over several weeks.

Why do agencies leave WP Engine with a full book of client sites?

Agencies usually leave WP Engine for three reasons: plan tiers that jump in price when you outgrow a site or visit cap, support that doesn't know your clients, and lingering doubt after the 2024 WordPress.org dispute. With 40 sites on one account, each of those problems multiplies by 40.

The tier structure is the first friction point. WP Engine's shared plans bundle a set number of sites with caps on visits, storage and bandwidth. That works when you have 8 sites and steady traffic. With 40 sites, a single client's successful campaign can push the whole account toward an overage or an upgrade, and the agency eats the difference because the client never saw a hosting invoice.

The dispute is the second. In September 2024, WordPress.org blocked WP Engine from its plugin and theme update servers, and WP Engine had to stand up its own mirror so customer sites could keep updating. A federal court ordered access restored in December 2024. The sites kept running, but plenty of agency owners spent that autumn explaining to clients why their host was in the news, and some decided they'd rather not repeat the conversation.

None of this makes WP Engine a bad host. It makes it a host whose pricing model assumes you'll manage the book yourself.

What does a pooled hosting plan cost compared with per-site hosting?

A pooled plan costs less on the invoice and more in agency hours. Per-site hosting costs more on the invoice but maps one hosting bill to one client, so the client pays for it through a care plan. The right choice depends on whether hosting is a cost you absorb or a service you sell.

Here's a worked example for a 40-site agency. Every number marked "assumed" is an illustration, so swap in your own. Labor is priced at $100/hr, and per-site hosting at TopSyde Complete's $71 a site, its rate for 11 to 99 Complete sites. Basic, which leaves out the built-in tools and the developer hour, is a flat $59 a site, or $2,360 a month for all 40.

Pooled plan, agency paysPer-site managed, client paysSplit: 12 critical sites per-site
Monthly hosting bill$500 (assumed)$2,840 (40 × $71)$852 (12 × $71) + $250 pooled (assumed)
Agency hours on hosting issues15 hrs (assumed)4 hrs (assumed)7 hrs (assumed)
Labor cost$1,500$400$700
Billed to clients$49/mo × 40 = $1,960$149/mo care plan × 40 = $5,96012 × $149 + 28 × $49 = $3,160
Net to agency per monthabout -$40about +$2,720about +$1,358

The pooled column is where most agencies sit, and the labor line is the one they don't track. Those 15 hours are plugin updates that broke a contact form, a client emailing "the site's down" at 7pm, a restore after someone deleted a page, a certificate that didn't renew on a domain the client moved without telling you. Each is small. Across 40 sites they add up to a part-time job nobody is paid for.

The split column is the one I'd start most agencies on. Not every brochure site for a local accountant needs managed hosting with monitoring and malware response. The 12 sites that take orders, book appointments or generate leads do, and those clients will usually pay for it once you explain what it covers. The other 28 can stay pooled somewhere cheap, get consolidated, or get a polite sunset notice if the client stopped paying years ago.

Whether a client accepts a $149 care plan is a sales question, and we've written up how Juniper Web Studio turned 28 forgotten client sites into $2,900/mo in recurring profit if you want the playbook.

What happens on a pooled plan when one client site goes wrong?

On a pooled plan, one site's problem can become every site's problem. Shared resources mean a traffic spike or bot flood on one site slows the others, and one account means one billing relationship, one login and one point of failure for the entire client book.

Agencies tend to think about this as a performance issue: the WooCommerce client runs a flash sale and the dentist's site crawls. That's real, but it's the mild version. The serious version is concentration risk. If the account is suspended over a failed card, flagged for abuse because one site got compromised, or damaged by a support action, all 40 clients call you on the same morning.

That last scenario isn't hypothetical. One agency owner described how a hosting support team wiped an entire server of client sites during what should have been a routine ticket. Hosts also go dark for days, as customers found during the UltaHost multi-day outage, and occasionally they disappear entirely, which is what happened to customers when a web host shut down and took the sites with it.

Per-site hosting doesn't make any of that impossible. It limits how far one incident spreads, which matters more as the book grows.

How do you stagger a 40-site migration?

Stagger a 40-site migration in four or five waves over 6-8 weeks. Start with an inventory, move a few low-risk sites to learn the new host, batch the bulk of brochure sites where you control DNS, then handle client-controlled DNS and finally the stores and membership sites in quiet windows.

WaveSitesWhat movesWhy this order
0All 40Nothing. Inventory onlyYou find the surprises before they find you
13-4Your own site and two or three low-traffic brochure sitesYou learn the new host's quirks on low stakes
215-20Brochure and lead-gen sites where the agency controls DNSBatches of 4-5 per week, no client coordination
38-10Sites where the client owns DNS or the registrar loginNeeds the client's calendar and credentials
44-6WooCommerce, membership and booking sitesLow-traffic window, order freeze, extra testing

Wave 0 is the one agencies skip, and it's the one that saves the project. For each site, record the registrar, who controls DNS, where email is hosted, which SMTP plugin or service sends transactional mail, any server cron jobs, pinned plugin versions, and whether the client has a login to anything you'd need. A spreadsheet with 40 rows and 12 columns takes an afternoon and prevents most of the late-night calls.

For the per-site steps (export, import, search-replace, testing on a temporary URL), our guide on how to migrate a WordPress site without breaking it covers the sequence, so I won't repeat it here. If you're also rethinking how you manage updates and staging across the book once it lands, the WordPress agency workflow for managing multiple client sites is worth reading before Wave 2.

Keep the WP Engine account live until the last site in Wave 4 has run cleanly on the new host for at least a week. If you're on an annual term, plan the waves backward from the renewal date so you aren't paying for a full extra year to cover two stragglers.

How do you keep client DNS and email working during the move?

Client email keeps working through a host move as long as the MX, SPF, DKIM and DMARC records stay intact. Changing only the A or CNAME record for the website leaves email untouched. The risk comes when you change nameservers and someone rebuilds the DNS zone by hand.

WP Engine doesn't host email, so your clients' mailboxes already live somewhere else: Google Workspace, Microsoft 365, the registrar, or an old cPanel account nobody remembers. That's good news. The website move doesn't touch the mailbox at all, provided DNS stays correct.

Here's how the record-level details go wrong in practice:

  • Nameservers move to a new DNS provider and the zone gets retyped instead of imported, so a DKIM selector or a second MX record goes missing.
  • A long DKIM TXT record gets truncated during copy and paste, and mail starts landing in spam a day later.
  • The SPF record lists the old server's IP because the site used to send mail directly, and nobody updates it after the move.
  • TTLs are left at 24 hours, so a mistake takes a full day to correct.

The fix is boring. Export the zone file before touching anything, lower TTLs to 300 seconds 48 hours ahead of cutover, and compare old and new zones record by record after the change. If you want a plain-language refresher on record types, our DNS guide for WordPress site owners covers it.

Deliverability rules have also tightened since many of these sites were built. According to Google's email sender guidelines (2024), anyone sending more than 5,000 messages a day to Gmail accounts must authenticate with SPF, DKIM and DMARC, and Yahoo enforces matching rules. Most client sites don't send that volume, but a store with order confirmations and a newsletter can, and a broken DKIM record after a migration hits exactly those messages. Routing site mail through a dedicated sending service, kept separate from marketing mail as described in our post on transactional versus marketing email, takes the host out of the email equation entirely.

How do SSL certificates and backups carry over between hosts?

SSL certificates don't transfer between hosts; the new host issues fresh ones. Get them issued before cutover using DNS validation or host pre-provisioning so visitors never see a warning. Backups also stay behind, so download a full copy of every site to storage you control before each wave.

Certificate gaps are the most visible migration failure. Point DNS at the new server before a certificate exists, and the first visitors get a browser warning that clients will screenshot and email you. Ask your new host whether it can issue certificates before DNS changes, and confirm each site loads over HTTPS on the new server using a hosts-file override before you flip the record.

Certificate management is also getting more frequent. According to the CA/Browser Forum's Ballot SC-081 (2025), the maximum lifetime of a public TLS certificate drops in steps to 47 days by March 2029. Across 40 sites, that's a lot of renewals, and any host you pick needs to automate them and alert someone when one fails.

On backups, WP Engine lets you download backup points as archives. Pull a full files-and-database copy of each site right before its wave, store it outside both hosts, and keep it for at least 90 days after you cancel. A backup that lives only inside the host you're leaving disappears when the account closes.

What should you ask a WP Engine alternative before signing?

Ask any WP Engine alternative how fast a human responds, what it monitors, how often it backs up and whether you can export those backups, how it handles malware, and what leaving looks like. With 40 client sites, the exit terms matter as much as the entry price.

The questions I'd put to every shortlisted host:

  • What's the support response time, during which hours, and is it written into an SLA?
  • What runs 24/7: uptime checks only, or also checks for broken forms, expired certificates and malware?
  • How often are backups taken, how long are they kept, and can I download them to my own storage?
  • Who removes malware if a site is compromised, and is that included or billed per incident?
  • Is pricing per site, per account, or per resource, and what happens when one site's traffic doubles?
  • Can I white-label the dashboard and reports for clients?
  • If I leave, how do I get every site and backup out, and how much notice is required?

For what it's worth, here's how we answer. TopSyde starts at $59/mo per site on Basic. A site-down ticket is answered within 15 minutes, 24/7, and other tickets within the response times published on our SLA page: an hour for a broken checkout or form during business hours, one business day for other issues and change requests. Monitoring runs 24/7, and malware detection and removal is handled by TopSyde Sentinel. Backup frequency, retention and the rest of the server details are on the spec sheet, and if you want to see how we stack up against WP Engine and others line by line, our hosting comparison page lays it out.

We're per-site by design, which means we're the wrong fit for the 28 brochure sites in the split model above and a reasonable fit for the 12 that make your clients money.

How do you turn a host migration into recurring revenue?

A migration gives you a reason to contact all 40 clients, which most agencies haven't done in years. Use it to reprice: explain what's changing, what the new hosting covers, and offer a care plan that bundles hosting, updates and support at a monthly rate the client pays directly.

Most clients on a pooled plan don't know who hosts their site or what it costs. The migration email is the first time many of them will hear about it, and it can do two jobs at once. It tells them about the move and the date, and it introduces a care plan with a clear list of what's included: monitoring, backups, security response, a set number of small edits per month.

Some clients will say no, and that's useful information. A client who won't pay $49 a month for hosting on a site you've maintained for free since 2019 is a client you can migrate to the cheapest tier or hand off. The ones who say yes become the recurring revenue base that makes the next round of web agency client acquisition less urgent.

Our hosting for agencies page covers white-label options and how we work with portfolios, and the case studies show what other agencies did after moving. If you want to test us before committing a whole wave, start with your own site or the Wave 1 group. Monthly Complete plans start with a 30-day free trial, so you can run a few real sites on the new setup before you move the clients who pay the bills.

Frequently Asked Questions

How long does it take to move 40 client sites off WP Engine?

Plan for 6-8 weeks if you stagger the work in waves. The inventory takes a day or two, brochure sites can move at 4-5 per week, and the stores and client-controlled DNS sites take longer because they depend on other people's schedules.

Will my clients' email stop working when I change hosts?

Not if the MX, SPF, DKIM and DMARC records stay intact. WP Engine doesn't host email, so changing the website's A or CNAME record leaves mailboxes alone. The risk comes from changing nameservers and rebuilding the DNS zone by hand, so export the zone file first and compare records after the change.

Is per-site hosting more expensive than a pooled WP Engine plan?

On the invoice, yes. Forty sites on TopSyde Complete at $71 a site is $2,840 a month, far more than a pooled plan. The comparison changes once you count the hours your team spends on hosting issues and bill the hosting to clients through care plans, which is why many agencies put only their revenue-critical sites on per-site hosting.

Should I cancel WP Engine before or after migrating?

After. Keep the account live until the last site has run cleanly on the new host for at least a week, and download full backups of every site to your own storage before you cancel. If you're on an annual term, schedule the waves so the final cutover lands before the renewal date.

Can I white-label TopSyde hosting for my clients?

Yes. Every account shows your logo and colors in the portal. With a white-label setup on your own domain, which we configure with you, the reports, emails and sign-in page carry your name too. Our agency page covers the options and how we handle client portfolios.

Rachel Nguyen
Rachel Nguyen

Senior WordPress Engineer

8+ years WordPress & WooCommerce development

Rachel is a senior WordPress engineer at TopSyde specializing in WooCommerce performance and plugin architecture. She has built and maintained high-traffic e-commerce sites processing millions in annual revenue.

Related Articles

View all →

For agencies

Managing WordPress for clients?

White-label portal, volume pricing that drops as your portfolio grows, and a senior developer behind every site. Your clients see your brand. We do the work.

Complete $89 a site a month · Less from 11 sites · Free migration · 30-day free trial