---
title: "PRM Migration: Moving Partners and Deal History"
url: https://www.fours.com/resources/blog/prm-migration/
canonical: https://www.fours.com/resources/blog/prm-migration/
type: Blog
description: "Move a partner program off a spreadsheet or another PRM: the order to load partners, contacts and deal history, and what must not fire on the way in."
---

# PRM Migration: Moving Partners and Deal History

> Canonical HTML version: https://www.fours.com/resources/blog/prm-migration/

1.  [Home](/)
2.  [Resources](/resources/)
3.  [Blog](/resources/blog/)
4.  PRM Migration: Moving Partners and Deal History

# PRM Migration: Moving Partners and Deal History

Move a partner program off a spreadsheet or another PRM: the order to load partners, contacts and deal history, and what must not fire on the way in.

[![Sabrina Xie](/authors/sabrina-xie.jpg)](/resources/blog/author/sabrina-xie/)

[Sabrina Xie](/resources/blog/author/sabrina-xie/)

Nov 5, 2026

 ![PRM Migration: Moving Partners and Deal History](/images/blog/prm-migration/hero.png)

A PRM migration is finished when every partner, contact and deal from the old system sits in the new one, attached to the right partner with its stage and dates intact, and nobody at a partner noticed it happen. No welcome email went out. No commission was calculated on a deal that closed last year. No partner you dropped came back. Getting there depends far more on the order you load records in, and on what you stop from firing while they load, than on the tool you are moving to.

This is a cutover plan for moving a partner program off a spreadsheet or another partner relationship management (PRM) system. Two lists sit at its core: what must carry over, and what must not fire on the way in.

## In what order does a PRM migration load records?

Load partners first, then contacts, then open deals, then closed deals. Every contact and every deal names a partner, so nothing else can attach until the partners exist, and closed deals go last because the ones you load with commission usually point at the partner record the new system has just created.

| Order | Record | Key it on | What must carry over | What must not fire | How to verify |
| --- | --- | --- | --- | --- | --- |
| 1 | Partners | Company domain, not company name | Tier, partner manager, the link to the partner’s CRM account | An invitation or welcome email to anyone at the partner; a partner you deactivated coming back | Partner count matches the source; one partner per tier checked for tier, manager and CRM link |
| 2 | Contacts | Email address, per partner | Name, title, role, and the partner they belong to | A portal invitation or any other email to the contact | Contacts per partner match the source; no partner address in the send log |
| 3 | Open deals | CRM opportunity ID | Stage, close date, registration date, deal value, the owner on your side, the partner | A notification to the partner; a second copy of the deal on re-upload | Open pipeline by partner matches the source; a re-uploaded deal leaves the count unchanged |
| 4 | Closed deals | CRM opportunity ID | Won or lost stage, close date, registration date, lost reason; commission only where you decided it | A commission on a deal you already paid; a notification about a deal that ended months ago; a second copy on re-upload | Won value by partner and year matches the source; the commission ledger holds only the deals you meant to load with commission |

Three things in that table carry most of the risk.

**The partner key is the domain.** Names drift: “Globex”, “Globex Inc.” and “GLOBEX” are one partner to a person and three to an importer. A company domain such as `globex.example`, once it is written one way and deduplicated (step 2 of the checklist), is far harder to vary, so it keys the partner and anchors its contacts and deals.

**The deal key is the CRM opportunity ID.** It lets you upload a fixed batch again without creating a second copy of every deal in it, and it ties each deal in the PRM back to the opportunity your sales team reports on.

**Closed deals are a choice, made per deal.** A deal can come across as a silent record, at its stage and dates, with no commission and no notification. That is the right default for history you have already paid out. Or it can come across with its commission amount, for a deal whose commission is still owed or belongs in the partner’s commission history. Give each deal one route, never both.

## Four decisions to make before you export

Settle these before anyone opens the export, because each one changes what goes in the file.

**1\. Which partners sync and which import.** If your partners already sit in Salesforce as accounts, [sync partners from Salesforce](/resources/blog/partners-already-in-salesforce/) as well: an import is a snapshot, and a sync keeps picking up the partners your reps create next quarter. But a sync lists those accounts for you to invite, which is the step this plan leaves for last, and it doesn’t bring their contact lists or deal history. So import every partner whose contacts or deals come across, Salesforce ones included, with its CRM account ID, and let the sync surface the partners created after the cutover.

**2\. Which side registered each historical deal.** Decide which side registered each historical deal before you export it; source credit is what a migration most often flattens. A spreadsheet tends to record the rep who owned the opportunity, an old PRM records who submitted the registration, and the two disagree on exactly the deals that decide tier credit and commission disputes. Put the answer in its own column, so the decision is on record whatever the destination does with it.

**3\. Which closed deals carry commission.** Split closed deals into two lists: history to record silently, and deals to load with a commission amount. Keep the lists disjoint. Nothing guarantees that two different importers recognize each other’s deals, so a deal on both lists risks a second copy.

**4\. What happens to partners you dropped.** A partner you deactivated in the old system is just another row in an export. Take dropped partners out of the file, and decide before the upload which ones, if any, come back. Reactivating a partner should be someone’s decision, not a side effect of a spreadsheet.

One prerequisite is mechanical: add every partner manager as a user in the new system first. A partner manager column points at a teammate, and someone who isn’t one yet has nothing to point at.

## The cutover checklist

Run these in order. Steps 5 to 7 repeat once per batch.

1.  **Export with CRM opportunity IDs.** Every deal row carries its opportunity ID from the CRM, and every partner row its CRM account ID where one exists. A deal without an ID can only be matched on its name and customer, which is how duplicates start.
2.  **Clean the domains.** One partner, one domain, written one way: lowercase, no `www.`, no path. Remove duplicate partners, your own company’s domain (an internal address on a partner row is a common slip), and personal email providers such as Gmail, which name a person’s inbox rather than a company.
3.  **Settle deactivated partners.** Apply decision 4: out of the file, or reactivated on purpose before the upload.
4.  **Correct existing partners by hand.** If some partners are already in the new system, from a pilot, a sync or an earlier batch, expect the import to leave what they have alone. A careful importer fills only the empty fields on a partner that already exists and never overwrites one someone has set, so a wrong tier there is fixed on the record, not by uploading a corrected file.
5.  **Batch to the destination’s limits, and schedule the reviews one after another.** Find out how many rows a file takes and whether each upload waits for approval. At 1,000 rows a sheet with one import pending at a time, a sample program of 140 partners, 620 contacts and 2,300 deals (700 open, 1,600 closed) takes three uploads: every partner, every contact and the open deals first, then the closed deals in two batches. That is three reviews in a row, and the cutover date has to allow for each. A batch’s contacts and deals can name only partners that already exist or that the same batch adds.
6.  **Check every batch row by row.** Each row should end in one of four states: created, already there, excluded, or failed. Reconcile the four with the row count of the file before you start the next batch.
7.  **Re-upload a fixed batch.** Correct the failed rows in the file and upload it again. Matching on the CRM opportunity ID means the deals that already loaded come back as existing rather than as copies.
8.  **Invite partners last, as a step of its own.** Once the data checks out, invite partners deliberately, by tier or by partner manager, with a note that says their deal history is already there. An import that invites nobody is what lets you choose that moment.

## What goes wrong in a PRM migration

Each failure below traces back to a step above, and each is cheaper to prevent than to unwind.

-   **One partner becomes three.** The import keyed on company name. Key on domain.
-   **Partners get a welcome email halfway through the migration.** The importer treated each new partner as a sign-up and ran onboarding. Use an import that creates partners with no members and sends nothing, then invite them yourself in step 8.
-   **Commission appears on deals paid last year.** Closed-won history went in through a route that runs commission rules. Record history silently, and load commission only on the deals in your commission list.
-   **Every deal arrives twice.** A batch went up again with no stable key. Put the CRM opportunity ID on every deal row.
-   **A partner you dropped is active again.** The file still carried it. Settle deactivated partners first; a safe importer refuses the row instead of reactivating the partner.
-   **Partner-sourced deals read as your own.** Attribution was flattened on the way out of the old system. Record which side registered each deal before the export, not after.
-   **Corrections don’t stick.** The importer fills only empty fields on partners that already exist. Fix those records by hand.
-   **The cutover slips a week.** Batches queued behind reviews nobody scheduled. Count the batches before you set a date.

## How to verify the load

Verification is a reconciliation against the source, run after every batch and once more at the end. Four checks cover it.

-   **Counts.** For each sheet, the rows in the file equal created plus existing plus excluded plus failed. Partners, contacts per partner and deals per partner each match the source.
-   **A sample per tier.** Open one partner from every tier and compare its tier, partner manager, CRM account link, contacts and deals with the old system.
-   **Pipeline and history.** Open deal value by partner, and won value by partner and year, match the source.
-   **Nothing fired.** Your email provider’s send log shows nothing to a partner address during the load, the commission ledger holds no new rows beyond your commission list, and no partner has a notification about a deal from the file.

## How the Fours partner import handles a migration

The Fours partner import, documented in [Import Partners, Contacts and Deal Registrations](https://doc.fours.com/prm/import-partner-data/), is built for a move off another PRM or a spreadsheet. It sits under Partners → Settings → Import Data, needs an Admin or Editor role, and takes one Excel template built for your organization, with sheets for Partnerships, Contacts and Deal registrations and an Allowed Values sheet that feeds the picklist dropdowns. A partner is identified by its company domain. A new partner gets an active partnership and a Fours organization with no members, “so nobody at the partner is invited or emailed”; contacts are added with nobody emailed; and “Deals are recorded silently, at their stage and registration date, with no commission and no notifications.” Because `crm_opportunity_id` identifies a deal, uploading the same ID again never creates a second one.

Fours checks every row before you submit and marks as invalid the rows a migration most often gets wrong: your own organization’s domain, a personal email provider such as Gmail, a domain that belongs to another customer’s Fours organization or matches more than one, a partner you deactivated (“reactivate the partner first”), a contact or deal for a partner that isn’t active unless the same upload’s Partnerships sheet adds it, and duplicates. Each sheet takes up to 1,000 rows. Fours reviews each import before anything is added, and you can submit one import at a time, so the batch plan in step 5 applies as written. History → Details then shows each row as Created, Existing, Excluded or Failed, with the reason.

Closed deals whose commission you want on record take a different route: Import Historical Co-Sell Referrals, under Partners → Settings → Co-Sell. It takes a commission amount as a flat figure in the deal’s currency, so a percentage arrangement has to be worked out first, and it names each partner by its Partnership ID, so it runs after the partners exist. Its records are created silently too. Neither page says whether the two imports recognize each other’s deals, which is one more reason to give each deal one route.

Some of the move stays with you. A partner you already have in Fours keeps what it has, because the import only fills in fields that are empty, so a correction to one of those is made on the record. Nobody is invited until you invite them. The batch schedule and the reconciliation are yours to run. The rest of the program, from the partner portal to tiers and commissions, is on the [Fours partner relationship management](/prm/) page.

If the partner program is moving as part of a wider platform change, the [cloud marketplace platform migration checklist](/resources/blog/cloud-marketplace-platform-migration/) covers listings, private offers and metering, and [how a switch to an indirect revenue platform runs](/switch/) sets out the rest of the plan.

## Sources

Primary sources for the platform rules cited above. Last verified November 6, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.

-   [Fours docs: Import Partners, Contacts and Deal Registrations](https://doc.fours.com/prm/import-partner-data/) — Fours behaviour: Partners → Settings → Import Data and its per-organization template with an Allowed Values sheet; a partner identified by its company domain; a new partner given an organization with no members, so nobody is invited or emailed; contacts added with nobody emailed; deals “recorded silently, at their stage and registration date, with no commission and no notifications”; crm\_opportunity\_id never creating a second deal; up to 1,000 rows a sheet; the invalid rows (own domain, personal email providers, another customer’s organization, a deactivated partner, an inactive partner, duplicates); one import at a time, each reviewed by Fours; an existing partner keeping what it has; History → Details with Created, Existing, Excluded and Failed
-   [Fours docs: Set Up and Manage Commission Plans (Import Historical Co-Sell Referrals)](https://doc.fours.com/prm/commission-plans/#import-historical-co-sell-referrals) — The route for past deals with commission: Partners → Settings → Co-Sell, a Partnership ID on every row, Commission Amount as a flat amount in the deal’s currency, and records created silently with no partner notifications
-   [Fours docs: Sync Partners from Salesforce](https://doc.fours.com/prm/sync-partners-from-salesforce/) — For partners already stored in Salesforce: the object, the filter that identifies a partner, matching accounts surfaced under Partners → Partner Discovery → From Your CRM with the email used to invite them, and the Partner Manager taken from the Account owner
