Moving over without trusting the numbers blind — and leaving if you need to.
Familiar charts don't guarantee identical numbers. Identity resolution, time zones, funnel windows, cohort membership and deletion rules all differ between tools. A migration is a reconciliation exercise first, a cutover second.
The path
- Inventory. List the metrics, funnels, cohorts and dashboards your team actually uses. Most teams find a short list that matters and a long tail that doesn't.
- Map events and identities. Match your current events to the event store DepSmith reads. Agree how anonymous and signed-in users are joined, which time zone days are counted in, and how deletions are handled.
- Reconcile a sample. Pick a representative set of reports, run them in both tools for the same period, and explain each difference. Some differences are correct — a definition was ambiguous before. Others are errors to fix.
- Run in parallel. Both tools run side by side for an agreed period, with the reconciled definitions in DepSmith's catalog.
- Cut over, with a rollback. Choose a date. Keep the incumbent available until the first review cycle on DepSmith has gone cleanly.
History that lives only in your current vendor
If your event history already lands in a store you control, DepSmith reads it from day one with no backfill. If the history exists only inside Mixpanel or Amplitude, it has to be exported into your store first. Both vendors offer exports, but how complete and how fast they are varies by plan and volume. We confirm the path for your setup before you commit.
What a pilot agrees up front
- The reconciliation sample, and what "matches" means for each report — exact, or within a stated tolerance.
- The questions the team will ask, including some the catalog can't answer yet.
- How much analyst review the definitions need, and who does it.
- Query latency and the extra warehouse cost, measured rather than estimated (see the pricing method).
- The exit checklist below.
We don't promise that every feature or every number will be the same as in your current tool.
Exit
Your raw events never moved, so there is nothing to retrieve. Some application state does live in DepSmith:
| What | Exportable? |
|---|---|
| Raw events | Already yours, in your store |
| Catalog definitions (metrics, dimensions, cohorts, funnels) | Yes — readable text |
| Approval history of definitions | Open: format to be confirmed |
| Saved reports and dashboards | Open: not yet exportable in a documented format |
| Users and permissions | Open |
| AI investigation records | Open — the AI analyst is in build |
To remove DepSmith: export what you need, delete the deployment from your account, revoke its warehouse role and any cloud IAM roles, and confirm with us that no support material is still held (see the Security page).
Questions this page doesn't answer are the ones we want to hear. Ask on a call, or write to contact@depsmith.com.
Request a demo