Keep WP Umbrella.See your whole agency.

Don’t replace WP Umbrella — plug it in

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

WP Umbrella is excellent at WordPress care plans: safe updates with visual regression, encrypted backups, Patchstack vulnerability monitoring, and client reports at EUR 1.99/site. Keep it.

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

What imports — and what stays in WP Umbrella

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

WP Umbrella’s API doesn’t expose backup or uptime-history data, so Burrow doesn’t pretend to have it. What it does expose — update proof and vulnerability data — 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 Umbrella connection. Connect the API today with zero installs; add the plugin later, per site, only where form and commerce visibility earns its keep.

Ask questions WP Umbrella’s AI can’t answer

Their agent sees maintenance data. Burrow’s MCP sees the whole client.

WP Umbrella ships an official Claude skill — if you’re reading this, you’ve probably tried it. It’s good at maintenance questions: which sites need updates, what vulnerabilities are open.

Now ask: “Which clients are behind on updates, had downtime this month, and haven’t been invoiced yet?” That question spans three systems. A maintenance agent structurally can’t answer it. Burrow’s MCP can, because the client record joins update status with Harvest invoices, GitHub activity, and analytics. If you already run Claude or Cursor against your tools, this is the integration that makes the cross-domain questions work.

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 Umbrella) next to Craft sites, Next.js apps, Shopify stores, GitHub activity, analytics, and invoices — organized by client, not by site. A client with a marketing site, a store, and a staging environment is three rows in a WP dashboard. In Burrow it’s one client, with billing and repos attached.

Know which clients are worth keeping

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

WP Umbrella tells you a site is behind on updates. 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 Umbrella.

Reports that justify the whole retainer

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

WP Umbrella reports show updates applied, uptime, and visual-regression passes — 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 Umbrella shows all 45 sites green. Care plans are running smoothly. But quarterly retainer reviews take a full afternoon: WP Umbrella report here, GitHub activity there, Harvest hours in a third tab, and a gut feeling about which clients are actually profitable. One client has been quietly consuming double their retainer hours for three months. Nobody noticed, because no single tab shows it.

After Burrow: The same 45 sites import via one API token. Each client’s card shows update status from WP Umbrella next to logged hours, invoice status, and deploy activity. The over-serviced client surfaces in the first week — 31 hours against a 12-hour retainer. That conversation happens in month one instead of at renewal, with a timeline to point at.

How Burrow fits with WP Umbrella

Run both. Use WP Umbrella for updates, backups, and care-plan delivery. Use Burrow for the unified client view, profitability visibility, and retainer-grade reporting.

Compare Burrow vs WP Umbrella | Maintenance reporting | All integrations