Keep WP Remote.See your whole agency.

Don’t replace WP Remote — plug it in

WP Remote keeps doing the work. Burrow becomes where you look.

WP Remote sits on the BlogVault and MalCare stack agencies already trust for updates, incremental backups, and security. Keep it. We have no interest in rebuilding backup infrastructure — yours works.

Burrow is where the owner looks when the question isn’t “did the backup pass?” but “which clients are healthy, profitable, and actually delivered this quarter?”

What imports — and what stays in WP Remote

We’d rather be precise than impressive. Here’s exactly what the integration covers:

One honest limit: uptime via the API is current status as of last sync, not a full incident history. We won’t oversell it. What the API does share — backup history and security detections — lands in your client’s timeline next to everything else.

Optional: go deeper with the Burrow plugin

The connection installs nothing. The plugin is there when you want more.

Some signals no maintenance platform API can see: whether the contact form actually delivered a lead, whether the WooCommerce checkout completed. For sites where that matters, the Burrow WordPress plugin captures form submissions from Gravity Forms, Fluent Forms, Ninja Forms, and Contact Form 7, plus WooCommerce order and checkout events — with history backfill on install.

It’s entirely optional and separate from the WP Remote connection. Connect the API today with zero installs; add the plugin later, per site, only where form and commerce visibility earns its keep.

One token. Your whole portfolio.

The connect is the pitch. WP Remote issues account-level tokens from My Account > API Credentials — no per-site setup, no child plugins to configure, nothing new installed anywhere.

Paste the token and Burrow imports sites and clients in one pass. Because WP Remote exposes client records via API, your client structure carries over automatically — you don’t rebuild anything. Two minutes from token to a populated dashboard is the honest expectation, not marketing rounding.

The rest of your portfolio, finally in the same view

Almost no agency is purely WordPress. Your maintenance dashboard will never show the headless build or the Shopify store.

Burrow puts your WordPress portfolio (imported from WP Remote) next to Craft sites, Next.js apps, Shopify stores, GitHub activity, analytics, and invoices — organized by client, not by site.

Know which clients are worth keeping

Site health is half the picture. Here’s the other half.

WP Remote tells you a site is behind on updates or had a failed backup. Burrow tells you that same client is also behind on invoices, logged 30 hours against a 10-hour retainer, and hasn’t had a deploy in two months.

Invoicing from Harvest, FreshBooks, or Tillage; code activity from GitHub; traffic from Plausible, Fathom, or GA — all joined against the client record you already keep in WP Remote.

Reports that justify the whole retainer

Maintenance reports prove maintenance. Your retainer is bigger than that.

WP Remote reports show updates applied, backups completed, and security scans — and they’re good at it. Burrow reports add what shipped (commits and pull requests), how traffic moved, and what was billed. When a client asks “what am I paying you for?”, you answer with the whole engagement — not just the care plan.

Before and after

Before Burrow: WP Remote shows every backup green and every site updated. But a client’s snapshot failed twice last month, their contact form quietly stopped delivering, and their invoice is 40 days overdue — three facts living in three different systems. You learn about the overdue invoice from your bookkeeper and the form from an annoyed email.

After Burrow: The same portfolio imports via one account token. The failed snapshots from WP Remote, the form-volume drop, and the overdue Harvest invoice all sit on the same client card. The Monday review takes ten minutes because the exceptions surface themselves — you’re reading one timeline, not reconciling five tabs.

How Burrow fits with WP Remote

Run both. Use WP Remote for updates, backups, and security. Use Burrow for the unified client view, profitability visibility, and retainer-grade reporting.

Compare Burrow vs WP Remote | Maintenance reporting | All integrations