Migration guide

Migrate from Whatagraph in a weekend

Move your Whatagraph data sources, dashboards, and client setup to SendBriefs's brief-first model. Step-by-step playbook in 6 hours.

~6 hours total·9 steps

The migration in 9 steps

  1. 01

    Export Whatagraph reports as PDFs (for reference)

  2. 02

    Catalogue your data sources + clients

  3. 03

    Reserve a Founders Circle seat at /early-access

  4. 04

    Reconnect data sources via OAuth

  5. 05

    Recreate top 2 templates from SendBriefs starters

  6. 06

    Migrate your top 5 clients with brand kits

  7. 07

    Run a side-by-side test cycle for one client

  8. 08

    Cut over remaining clients in batches

  9. 09

    Cancel Whatagraph subscription

Why teams switch#

Whatagraph is excellent at visualizing marketing data — clean charts, polished embeds, deep platform coverage. SendBriefs is excellent at shipping the narrative artifact — the brief your client opens on Monday, with charts inside it.

If your clients consume your reports as briefs (read, forwarded, archived), the visualization-first model leaves work on the table. The narrative is what they actually read; SendBriefs treats that as the product.

Before you start#

You need:

  • Admin access to your Whatagraph account
  • A list of your top 5-10 clients with their data sources documented
  • 4-6 hours of focused time

What stays the same#

  • Data source connections. Same Google/Meta/HubSpot/etc. OAuth flow.
  • Client roster. One-to-one mapping.
  • Brand kits. You'll re-upload logos and re-enter color hexes; the concept of per-client branding stays.

What changes#

  • Output shape. Dashboard-based reports become narrative-first briefs with embedded data blocks. Same numbers, different artifact.
  • Approval flow. Whatagraph doesn't have native approvals; SendBriefs ships with inline review + audit log out of the box. Treat this as a process upgrade.
  • Cost model. Whatagraph prices per agency-tier-with-features; SendBriefs prices purely per client. Most mid-market agencies see lower TCO on per-client.

Step-by-step walkthrough#

1. Export your existing Whatagraph reports as PDFs#

These are reference material, not import targets. You'll use them when recreating the templates to match the cadence and structure clients already expect.

2. Catalogue your sources + clients#

Build a migration spreadsheet:

client | sources | cadence | branding
Northway | GA4, Meta Ads | monthly | logo + 3 brand colors
...

3-9. Walk through the in-app onboarding#

SendBriefs's setup flow guides you through reconnecting sources, cloning templates, and batching the cutover. Each step has in-app help + live chat.

Common gotchas#

  • Widget-to-block translation. Whatagraph's widget library is rich; SendBriefs's block library is structured around the brief format. Some widgets have direct equivalents; some don't. The ones that don't are usually decorative — content that belongs in a paragraph, not a separate widget.
  • Per-client deliverable cadence. If different clients are on different cadences in Whatagraph, document them carefully — schedule mistakes during migration are the most common cutover failure.
  • Branded subdomain DNS. Whatagraph hosts on their subdomain; SendBriefs supports custom subdomains per client. Plan the DNS work into the migration if subdomain branding matters to your clients.

When to ask for help#

For >25 clients or non-standard integrations, apply to Founders Circle — we'll do hands-on migration for the first 5 clients.