# Should you migrate from Spiff? The room usually agrees commissions should be migrated into the opportunity before the quarter closes, before anyone has brought the plan into the room or named the record it reads. **Published:** 2026-05-11 **Canonical:** https://synconai.com/should-i-migrate-from-spiff **Author:** SynconAI Architecture Team ## In short Salesforce completed the Spiff acquisition on 1 February 2024. Spiff is incentive compensation. Do not invent a payout percentage. The plan stays until someone names the opportunity or the order it reads. An opportunity already stores an amount, a stage, and a close date. It does not calculate the plan. Keep the plan, use the record for the sale it already records, or keep both. ## Sources - **Salesforce Signs Definitive Agreement to Acquire Spiff** (retrieved 2024-02-01) https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-spiff/ > Salesforce completed its acquisition of Spiff on February 1, 2024. ## What to take away - The agreement that the opportunity amount is the payout is compatible with a pay day that had to be undone, and an amount is not a plan. - The acquisition completed on 1 February 2024. That date is not a rate card. Spiff is incentive compensation. No end date is given here. - Do not invent a payout percentage. The plan stays until someone names the opportunity or the order it reads, including the field it may see and the field it must not treat as pay. - An opportunity stores a deal. An order, where you use one, stores what was sold. Neither calculates pay. The choices are not ranked, and no listing is invented. ## The guide A sales manager asked for commissions to be migrated into Salesforce before the quarter closed. The reason was the acquisition. The opportunity amount would become the payout. Around the table everyone already agreed a number was needed, because a demo looked unfinished without one. Nobody had the plan in the room. A slide suggested a round percentage, because a round number looked finished. On pay day two reps were short and one was over. The opportunity had the right amount for the sale. It had never been the plan. The plan still lived where the rules were written. The invented percentage had been used as a migration. Payroll had to undo it. The agreement is the problem. It is easy to reach, and it fits a pipeline report, which is not a rule a payroll person can check. A wrong pay day is compatible with a plan you already pay people on, an opportunity that already stores an amount and a stage, an order that stores what was sold, and a completion date that contains no percentage. Only one of those is a decision about a named record. You do not type a rate into a field because a demo needed a number. What follows are the questions that separate those explanations. Each has a good answer and a bad answer, and the difference is whether the answer names something specific: a plan, an opportunity or an order, a field, a person who can refuse a percentage that is not in the plan. A general answer at this stage is what turns into a pay day that has to be undone. ::: warn Do not invent a payout percentage. The plan stays until someone names the opportunity or the order it reads. The completion on 1 February 2024 is not a rate card. No listing or shutdown date is invented here. ::: | Question | Who has to answer it | What a bad answer usually means | | --- | --- | --- | | 1. Which rule is supposed to move | The payroll person who can check the sentence | "The commission" is standing in for a rule | | 2. Which opportunity or order does the plan read | The person who owns the plan | All of them, or a record the org does not use | | 3. What do the opportunity and the order already store | The administrator who can open the deal | An amount is being multiplied into pay | | 4. What does the completion sentence contain | Whoever is filling the silence with a rate | A date is being read as a rate card | | 5. What must the plan refuse | Whoever put a percentage on the slide | History of pay is about to be backfilled from a guess | ## 1. Which rule is actually in the room? The question is not whether to migrate Spiff. It is a sentence a payroll person can check: this plan reads this opportunity, or this order, and it pays on this named basis. **A good answer sounds like** that sentence, written by the person who owns the plan, with the record named and the basis named, and with no percentage that is not already in the plan. **A bad answer sounds like** the commission, or Spiff, or a round percentage the slide invented. If you cannot write the sentence, you are not ready to migrate. You are ready to leave the plan where it is. A programme that starts by picking a rate for the demo has chosen the pay-day error. Send the slide back. Do not invent a payout percentage. Spiff is incentive compensation. Salesforce completed the acquisition on 1 February 2024. The product did not become the Opportunity object. A plan is a set of rules about what a person is paid when a sale meets those rules. The sale can be an opportunity or an order you name. Until you name it, the plan does not know what to read. The name you still use for the rules is the plan, not a stage on a pipeline report. Reps are paid from the plan you already run. If the plan is wrong, fix the plan. Do not fix it by typing a percentage into Salesforce and calling the type a migration. ## 2. Which record does the plan read? Stay when the plan is the plan you already pay people on. The completion did not rewrite the rules. It did not set a rate. An opportunity can tell you what was sold. It cannot tell you what the plan pays unless the plan says it reads that opportunity. Moving "commissions into Salesforce" without that sentence will invent a percentage. **A good answer sounds like** opportunity or order, the field the plan may see, the stage or status that means the sale counts if the plan says that, and the person who owns the plan and can refuse a percentage that is not in it. **A bad answer sounds like** all of them. If the answer is "all of them", you have not named the record. The plan stays put. The plan stays until someone names the opportunity or the order it reads. Naming an object you do not use is not naming it. If you do not use orders, say so. Do not create one so a demo has somewhere to point. Move one rule only after the opportunity or the order is named, including which field the plan reads and which field it must not treat as pay. Moving "all historical payouts into a custom object" is a paste. It is not the plan. When they name the record, write the field. Amount is not always the field. A discounted total, a line, or a date may be what the plan uses. Guessing "the amount" is another invention. Open the plan. Read the rule. Then point at the record. ## 3. What do the opportunity and the order already store? Name the native behaviour before you compare a plan with it. An Opportunity is a record of a deal in the org. It has a name. It has an amount. It has a stage. It has a close date. A seller updates those fields as the deal moves. A report can sum the amount. The opportunity does not contain a payout rule. It does not know a quota. It does not split an amount across two reps unless you have built that split on purpose, as data, not as a guess. That is what the opportunity already does. It records the sale you asked it to record. An Order, where your org uses one, is the other native record to name. It has a total and it has lines. It records what was sold after the steps your org already requires. It does not, by having a total, calculate what a person is paid. Payroll cannot read an order and invent the rate. **A good answer sounds like** an administrator who opened the opportunity or the order and named the amount or the total, the stage or the status, and said plainly that none of those fields is the plan. **A bad answer sounds like** a pipeline report called a compensation migration. If the need is "see the amount of open deals", the opportunity report already does that. Leave the plan out. If the need is "pay the rep", the opportunity is not the plan. Do not invent a payout percentage so the amount can be multiplied into a commission. A report of opportunity amounts is a report of sales. It becomes pay only when the plan says so, in writing, for a named record. If the fourth person, the owner of the plan, is missing, nobody is allowed to type a rate. The comparison starts after the four lines. A slide that says "versus native" and shows a percentage has skipped the native object and invented pay. ## 4. What does 1 February 2024 contain? Do not migrate because the company was bought. The completion was 1 February 2024. That is a date. It is not a rate card. The page cited here says the acquisition completed, and the sentence is quoted once: "Salesforce completed its acquisition of Spiff on February 1, 2024." The sentence does not contain a percentage. It does not say opportunities calculate pay. It does not give a shutdown. **A good answer sounds like** the completion left as a date, with the plan still the source of the rules, written by the person who owns the plan. **A bad answer sounds like** a payout invented to fill the silence. There is no end date for Spiff in the material this decision is allowed to use. Do not invent one, and do not invent a payout to fill the silence. The close is not a new rate. People who search for what the software is are asking about compensation, not about a CRM cutover. Answer with the plan. Then ask which opportunity or which order it reads. Do not backfill old pay from a percentage you made up this week. History of what people were paid is a payroll question. It is not a reason to stamp a new rate onto old opportunities. If the plan changes, the plan owner says from which deal the new rule applies. The 1 February 2024 completion does not say it. The quoted sentence has no rate in it. Your four lines do, or they do not, and if they do not you are not ready. ## 5. What is the plan using instead of the rule? **A good answer sounds like** a refusal, written by the plan owner, of four things: an invented percentage, a paste of historical payouts called the plan, a listing as the rate card, and a ranked shortlist. **A bad answer sounds like** a listing, or a league table of compensation tools. No listing is invented here. An app that calculates pay is not described. A catalogue page is not a decision. If a proposal cites a listing that was never named here, ask which opportunity or order it reads and where the percentage is written in the plan. Until they can, the listing is a rumour. The shapes here are not ranked. Keep the plan. Use the opportunity or the order for the sale it already records. Keep both, and write which record the plan reads. Firms are not ranked. Listings are not ranked. Two options can be compared by whether pay day has to be undone. A league table cannot. Stop after one rule. The next rule is the next decision. Cross out the payouts this decision will not touch. Read the sentence to the payroll person. If they cannot check it, the plan stays. ## What staying actually looks like All five answers are measured against an alternative, and the alternative is usually left unstated, which flatters the quarter close. State it. Staying means the plan remains the rules you already pay people on, and the opportunity or the order remains the sale it already records, until the plan names one of them. The cost of a false move is the pay day you already had: two reps short, one over, and a percentage nobody could find in the plan. There is a version of staying that is simply the correct decision. If the record is unnamed, typing a rate will not create a plan. An organisation that brings the plan into the room first reaches any later field with a sentence payroll can check. **A good answer sounds like** the rule, the opportunity or the order, the field, the person who can refuse a percentage, and a choice to keep the plan, use the record for the sale, or keep both, with a date and that person. **A bad answer sounds like** we cannot keep a compensation product after the close. The acquisition completed. It did not calculate pay, and it did not put a rate in the sentence. ## Where the neighbouring questions live Cost and hiring sit on [the Spiff implementation page](/spiff-sales-performance-management). The purchase story sits on [what happened to Spiff](/what-happened-to-spiff). The connector sits on [integrating Spiff with Salesforce](/integrating-spiff-with-salesforce). ## Questions ### Should I migrate from Spiff to Salesforce? Only for one rule in the plan, after someone names the opportunity or the order it reads and the field it may see. Salesforce completed the Spiff acquisition on 1 February 2024. Do not invent a payout percentage. The plan stays until that record is named. ### What is Spiff software now? Incentive compensation. The acquisition completed on 1 February 2024. A plan is rules about what a person is paid when a sale meets those rules. It did not become the Opportunity object. No end date is given here. ### How does Spiff compare with an opportunity? An opportunity stores a name, an amount, a stage, and a close date. An order, where you use one, stores a total and lines. Neither calculates the plan. Compare only after the plan names the record and the field. A pipeline report is not a compensation migration. ### What are the alternatives after the acquisition? Keep the plan, use the opportunity or the order for the sale it already records, or keep both and write which record the plan reads. They are not ranked. No listing is invented. An invented percentage is not an alternative. ### Where are cost, the acquisition story, and the connector? Cost and hiring are on the implementation page. The purchase story is on the what-happened page. How the plan reads a record is on the integration page. No price, no percentage, and no shutdown date are stated here. --- SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Sales Cloud (https://synconai.com/salesforce-sales-cloud-consulting).