Move from WP Remote without unpicking your backup strategy
WP Remote sits inside the BlogVault family and inherits real backup and security credibility. Migrating keeps that protection standard while simplifying the plan structure and adding the client-operations layer around it.
Assisted migration is free. We do the connection work with you.
Why agencies move on from WP Remote
WP Remote's strengths are inherited and genuine: BlogVault's backup engine behind it, MalCare's malware knowledge alongside it, and a security-led approach to agency automation. Sites protected by that stack are well protected, and we are not going to argue otherwise.
The friction agencies report is structural rather than technical. Capability is spread across tiers and across sibling products, so working out what is included at which price, and which product owns which feature, takes more effort than it should. The line between the free tier, the premium per-site tier and separately-sold infrastructure services is not always obvious until a bill arrives.
The second gap is the one most maintenance-first tools share: the product knows a great deal about site health and comparatively little about the business wrapped around it. Tickets, time, entitlements, SLA status and per-client margin sit outside the tool, which means the monthly client conversation is assembled by hand.
What the switch actually costs you
Your WP Remote account and any BlogVault backups continue running untouched. The two connectors coexist, so no site is ever unprotected during the transition.
- No DNS change, no hosting move, no downtime
- Sites stay connected to WP Remote 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 Remote
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 and group structure
- Team users and permissions
- Update schedules
- Backup frequency settings
- Uptime monitoring configuration
Rebuilt during onboarding
- White-label branding and sender domain
- Report templates and recipients
- Staging workflow preferences
- Care-plan entitlements and SLA thresholds
- Notification routing
Stays exactly where it is
- Your hosting provider and DNS
- Your WP Remote and BlogVault accounts
- Existing BlogVault backup archives
- Any MalCare protection you run separately
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 Remote 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 the portfolio. WP Remote supports bulk plugin deployment, so pushing our connector from your existing dashboard is the fastest route; a WP-CLI command is available as an alternative.
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 Remote active as long as you like. Most agencies run both for one billing cycle, confirm the backups and reports agree, then disconnect.
What changes after the move
Plan structure is the first thing agencies notice. Rather than a matrix of tiers and separately-sold services, management, monitoring, reporting and team access are included, with charges only for genuinely infrastructure-heavy usage such as very large backup volumes. Overages are published rather than discovered.
The second change is portfolio-level analysis. Instead of site-by-site status, the dashboard surfaces cross-portfolio patterns: which plugin is creating exposure across eleven clients at once, which backups have never been restore-tested, which sites have drifted outside their care-plan SLA, and what the team should work on first this morning.
The third is that the agency operations layer arrives: support requests, time against accounts, entitlement consumption and per-client profitability, all sitting alongside the technical record rather than in separate tools that do not talk to each other.
Where you may prefer to stay
Migration is not automatically the right call. Be honest about these before you move:
- You rely on BlogVault's real-time WooCommerce backup depth as a contractual promise
- You already run MalCare and want the whole stack from one vendor
- Your portfolio is small enough that the free tier covers you
- You have no interest in the operations layer and only need maintenance
We would rather you stayed on WP Remote than switched badly. Our WP Remote comparison sets out where it is genuinely the better product.
Questions about leaving WP Remote
Your existing BlogVault archives are unaffected and remain accessible through that account. Going forward, WPCentrify takes its own incremental encrypted off-site backups with scheduled restore testing. For most portfolios that is equivalent protection. If you specifically depend on BlogVault's real-time WooCommerce order-level backup, keep that account for those stores and use WPCentrify as the operations layer around it. That combination is supported and reasonably common.
Yes. The connectors are independent and there is no conflict. Run in parallel for at least one billing cycle before disconnecting anything.
That is the intent, and it is fair to hold us to it. Management, monitoring, reporting, team access and white-labeling are included rather than tiered. Charges apply only to infrastructure-heavy usage such as unusually large backup storage, and those rates are published on the pricing page rather than quoted on request.
WPCentrify detects and reports malware and known vulnerabilities across the portfolio and prioritises them by exposure. It does not perform hands-on malware removal, which is a specialist service. Agencies commonly pair us with a dedicated remediation service for that, and MalCare is a reasonable choice if you already use it.
Staging configuration preferences are rebuilt during onboarding rather than transferred. Existing staging sites created through WP Remote continue to exist on your hosting and are unaffected by migration.
A 30-site portfolio typically takes one working session: one to two hours for connector deployment, two to three hours for policies, reports and client mapping. Larger portfolios are staged in batches across several sessions.
Before you decide
WP Remote alternative
A balanced feature and pricing comparison, including where WP Remote 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 Remote 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.