NEW · MIGRATION CENTER

Your data. Out, and on its way.

Pull a partner program out of any PRM like PartnerStack, Mantle, Impact, Shoffi, or a spreadsheet — and land it wherever you’re going next. Complete, normalized, and counted back against the source.

We’re the layer in between. We move it, we prove it, and we don’t keep it.

Where we sit

We're not the destination. We're the road.

Partner data is trapped in systems that were never built to let it out cleanly. The Migration Center is a service, not a home — it reads from one system, normalizes what it finds, and hands the result to wherever you’re going. Including a competitor.

You're leaving
  • PartnerStack
  • Mantle
  • Impact
  • Shoffi
  • Spreadsheets & CSV · and more
In transit
Migration Center
Extract. Normalize. Reconcile. Deliver.
Retention · 0 days
You're going
  • Another PRM or affiliate platform
  • Your warehouse or database
  • Structured CSV and JSON
  • Your finance team's spreadsheet
  • Wherever you say · and more
Supported systems

Read from anything. Write to anywhere.

Most of these systems will export something. Very few will export everything, in a shape the next system can read. That gap is the whole job.

PartnerStack

Partners, groups, links, and referrals — plus the full commission ledger, including historical payout events.

Source Destination

Mantle

Subscription and referral records for Shopify app partners, mapped back to the installs that originated them.

Source

Impact

Media partners, contracts, tracking links, and conversion events with their attribution windows intact.

Source Destination

Shoffi

Affiliate rosters, referral codes, and commission history from Shopify-native programs.

Source Destination

Spreadsheets & CSV

The program that lives in a Google Sheet, a Notion table, and one person’s memory. We map it, then normalize it.

Source Destination

Something else

If it has an export, an API, or a database, it can move — in either direction. Tell us what you’re on.

What moves

The whole program — not just the parts that export cleanly.

Most exports quietly drop the records that are hard to map: historical payouts, expired links, partners who churned. Those are exactly the records that matter when someone asks you to prove a number.

ObjectScopeWhat's preserved
PartnersContacts, tiers, agreements
Active · dormant · churned
The date each relationship actually started, not the date it was imported.
PayoutsThe full commission ledger
Paid · pending · clawed back
Original amounts, dates, and statuses — including disputes, carried over as-is.
ReferralsLinks, codes, conversions
Converted · expired · open
Attribution windows preserved rather than recalculated against a new clock.
CustomersAccounts and identities
Matched · unmatched
Identity resolution across systems, with every unmatched account named, not silently merged.
How it works

Four steps. The last one is us disappearing.

A migration is a data problem before it’s a software problem. The mapping happens in the open, nothing is delivered until you’ve approved it, and nothing stays behind once it is.

01

Extract

We pull the complete record set from your source system through its API or export — including the objects most tools leave behind. Nothing is sampled.

02

Normalize

Fields are mapped to the shape your destination expects. Currencies, dates, statuses, and identities get resolved into one consistent set.

03

Reconcile

Every conflict surfaces as a named exception with the evidence attached. You clear the list. Then counts get checked back against the source.

04

Deliver & purge

Your data lands where you asked, with the manifest attached. Then we delete our copy. You get written confirmation that we did.

Custody · in detail

We hold it long enough to move it. Not a day longer.

Your partner data passes through us. It doesn’t live here. There’s no account to keep open, no dataset quietly retained for a future upsell, and no version of this where leaving costs you something.

When a record can’t be mapped cleanly, it becomes a named exception with the evidence attached and a decision for you to make — the same severity model you’ll recognize from Receipts. You clear the list. We don’t clear it for you, and we don’t discard what’s left.

  • Delivered in structured CSV and JSON, or written directly to your destination
  • A manifest with source counts and destination counts, side by side
  • Every exception named, with the record it came from
  • Our working copy deleted on delivery, with written confirmation
Exceptions
3 open · 58 cleared
Blocker
Payout with no partner record
$760 commission event references a partner ID that doesn't exist in the source export.
Warning
Rate shift mid-history
Subloop × Hartwell & Co. — 20% → 8% across 3 billings. Confirm which rate carries forward.
Info
Duplicate customer account
Two records resolve to the same domain. Merge, or keep both and flag the link?
Cleared
Currency normalization
58 records in GBP converted at the rate recorded on each event date, not today's.
Nothing delivers until this list is empty
Start here

Tell us where it's stuck. We'll tell you what moves.

A 30-minute scoping call starts with your current system and ends with a written record inventory. No commitment — and the inventory is yours either way.

migrate.yourpartnerpartner.com