Migration guide

Migrate from Reportz in a weekend

Move from Reportz's KPI-dashboard model to SendBriefs's brief-led reporting. Step-by-step migration playbook for 5 hours of focused work.

~5 hours total·9 steps

The migration in 9 steps

  1. 01

    Export Reportz dashboards as PDFs (reference)

  2. 02

    Catalogue KPI mappings + client list

  3. 03

    Reserve a Founders Circle seat at /early-access

  4. 04

    Reconnect data sources via OAuth

  5. 05

    Clone the SendBriefs starter templates (monthly + weekly)

  6. 06

    Migrate top 5 clients (brand kit + cadence + delivery)

  7. 07

    Run side-by-side test for one client

  8. 08

    Cut over remaining clients

  9. 09

    Cancel Reportz subscription

Why teams switch#

Reportz organizes everything around the KPI dashboard — clean per-KPI tiles, simple configuration, low ramp. SendBriefs organizes everything around the brief — the narrative artifact your client opens, with KPIs embedded inside it.

If KPI tiles are the deliverable for your client work, Reportz is a fine fit. If your clients need context alongside the numbers ("what does this mean?" "what are we doing about it?"), the brief format is structurally better.

Before you start#

  • Reportz admin access
  • KPI list + client roster
  • 4-5 hours of focused time

What stays the same#

  • Data source connections. Same OAuth flow.
  • KPI definitions. Whatever Reportz tracks, SendBriefs can pull as a live data token.
  • Client list + cadences.

What changes#

  • Deliverable composition. KPI dashboards become metric tiles inside a brief, with narrative blocks around them.
  • Per-client branding depth. SendBriefs supports per-client custom subdomains; Reportz white-labels at the workspace level only.
  • Approval flow. SendBriefs ships inline review + audit log; Reportz doesn't.

Step-by-step walkthrough#

1. Export your existing Reportz dashboards as PDFs#

Use them as reference when recreating templates. Each Reportz dashboard becomes a section (or two) in a SendBriefs brief.

2. Catalogue KPI mappings#

client | KPIs | sources
Acme   | sessions, MQLs, CAC, ROAS | GA4, HubSpot, Stripe, Google Ads
...

3-9. Follow in-app onboarding#

Setup flow walks you through OAuth reconnection, template cloning, and client migration in batches.

Common gotchas#

  • KPI-to-section mapping. A KPI grid in Reportz becomes a metric-tile block (or two) in SendBriefs, surrounded by narrative. The KPIs are the same; the surrounding structure is different.
  • Dashboard URL → brief URL. If clients had bookmarked Reportz dashboard URLs, those will break. Plan to send a "we've moved" email to each client during cutover.
  • Scheduling overlap. Cancel Reportz schedules before SendBriefs schedules fire.

When to ask for help#

For >25 clients or heavy custom KPI work, apply to Founders Circle for hands-on migration support.