Keep the safe updates, add the operations layer
WP Umbrella already does maintenance infrastructure well. Agencies move to WPCentrify when the missing piece stops being technical and starts being commercial: who asked for the work, how long it took, and whether the care plan makes money.
Assisted migration is free. We do the connection work with you.
Why agencies outgrow maintenance-only tooling
WP Umbrella is a genuinely good product and one of the few competitors that treats update safety as a first-class problem rather than a checkbox. Visual regression, automatic rollback, clear per-site pricing and a strong European data position are all real strengths, and agencies who leave rarely do so because the maintenance side disappointed them.
They leave when the shape of the problem changes. Maintenance infrastructure answers whether the site is healthy. Running a care-plan business also requires answering which client asked for this, how many hours went into that account this month, whether you are inside the SLA you sold, and whether the plan is profitable at the price you charge. Those questions live in a helpdesk, a spreadsheet and a time tracker, none of which know what the maintenance tool did.
WPCentrify's position is that the technical record and the commercial record should be the same record. When a support request, the time spent on it, the update that caused it and the client report describing it all sit in one system, the monthly report stops being a writing exercise and margin stops being a guess.
What the switch actually costs you
WP Umbrella and WPCentrify connectors coexist without conflict. There is no cutover moment and no point at which a site is unmonitored by both.
- No DNS change, no hosting move, no downtime
- Sites stay connected to WP Umbrella until you disconnect them
- Run both platforms side by side for as long as you want
- We delete nothing on the other side
What moves across from WP Umbrella
Some things transfer automatically, some are rebuilt during onboarding, and a few never move at all. Here is the honest split.
Transfers automatically
- Site list and URLs
- Client groupings
- Team members and roles
- Update schedules
- Backup frequency
- Uptime and PHP error monitoring configuration
Rebuilt during onboarding
- White-label report branding
- Report templates and recipient lists
- Care-plan entitlements and SLA thresholds
- Ticket categories, if consolidating a helpdesk
- Time-tracking categories and billable rates
Stays exactly where it is
- Your hosting provider and DNS
- Your WP Umbrella account and its history
- Backups stored in WP Umbrella
- Your existing client contracts
How an assisted migration runs
Most portfolios under fifty sites are fully connected within one working session. Larger portfolios are staged in batches so nothing is rushed.
Scoping call, 20 minutes
We look at your WP Umbrella setup together, count the sites, note the plans and groupings you use, and agree a batch order. Ecommerce and business-critical sites usually go last, once you have seen the workflow on lower-risk sites.
Bulk connector deployment
You install the WPCentrify connector across your portfolio. WP Umbrella supports bulk plugin installation, so the fastest route is pushing our connector from your existing dashboard. A WP-CLI command is available for portfolios managed via terminal.
Verification pass
Every connected site runs a first health check: WordPress version, plugin inventory, update backlog, backup presence, SSL expiry and an uptime baseline. You get a portfolio report before you have changed a single setting.
Policies and client mapping
We rebuild your update schedules, backup frequencies, client groupings, report templates and team permissions to match what you had, then automate the parts that were previously manual.
Parallel running
Keep WP Umbrella active as long as you like. Most agencies run both for one billing cycle, confirm the backups and reports agree, then disconnect.
What the operations layer adds
The first addition is that client requests become part of the same system. A support request arrives, is assigned, is worked on with time recorded against it, and appears in that client's monthly report next to the updates and incidents from the same period. Nobody re-types anything into a separate helpdesk.
The second is entitlement and SLA tracking. Care plans usually promise something specific: a number of support hours, a response time, a monthly report, a certain backup frequency. WPCentrify tracks consumption against those promises, so you find out you are over-servicing an account during the month rather than at renewal.
The third is profitability per account. Labour time, licence costs and infrastructure usage roll up per client, so you can see which care plans carry the portfolio and which quietly lose money. This is the part most maintenance tools do not attempt, and it is usually the reason agencies make the move.
Where you may prefer to stay
Migration is not automatically the right call. Be honest about these before you move:
- You only need maintenance infrastructure and have no interest in tickets or time
- Per-site flat pricing suits your portfolio shape better
- EU data residency is a requirement you have already solved with WP Umbrella
- Your helpdesk and time tracking already work well and you have no wish to consolidate
We would rather you stayed on WP Umbrella than switched badly. Our WP Umbrella comparison sets out where it is genuinely the better product.
Questions about leaving WP Umbrella
Yes. Visual comparison against key pages before and after an update is part of the safe-update workflow, alongside a pre-update restore point, health checks, form and checkout testing where relevant, and automatic rollback on failure. If visual regression is the specific capability keeping you on WP Umbrella, it is not a reason to stay.
Yes, and it is the recommended approach. The two connectors are independent. Run both for a billing cycle, compare the backup and monitoring records, then disconnect when you are confident.
Configuration transfers, archives do not. We take fresh full backups of every site during onboarding so you have verified restore points immediately. Keep WP Umbrella active until your new backup history is deep enough to satisfy your own retention policy.
Per site, often yes. WP Umbrella's flat per-site price is one of the simplest in the category and is hard to beat on maintenance alone. The comparison worth running is against your combined spend on maintenance plus helpdesk plus time tracking plus reporting, since WPCentrify is intended to replace several line items rather than one.
Data residency options are documented on our security page, along with what we store and where. If a specific residency guarantee is contractually required, confirm it with us in writing before migrating rather than relying on a marketing page.
For a typical 25 to 40 site portfolio, connector deployment takes one to two hours and policy rebuilding another two to three. Consolidating a helpdesk or time tracker into WPCentrify takes longer, and we plan that separately rather than doing it on migration day.
Before you decide
WP Umbrella alternative
A balanced feature and pricing comparison, including where WP Umbrella still wins.
Read the comparisonPricing
What WPCentrify costs at 10, 50 and 200 sites, with no per-feature add-ons.
See pricingSecurity practices
How connections are authenticated, what we store, and how to revoke access.
Read securityMove off WP Umbrella on your own schedule
Tell us how many sites you manage and we will plan the batches with you. No cancellation deadline, no forced hosting change.
Free during early access. No credit card required.