A "nonstandard" contract is any deal whose terms leave the approved playbook: an unusual discount, payment term, liability cap or a commitment about future product. These deals leave the richest records because someone had to decide, in writing, whether to accept them. A CPQ migration is the moment those decisions are most likely to become unreadable, because the project is scoped around quoting tomorrow, not explaining yesterday.
What should be inventoried before a CPQ migration affects nonstandard contract approval history?
List record classes, years covered, the owning system and the real access deadline for each, plus the approval matrix versions in force over those years. The deadline is the day the old CPQ objects or package are removed, not the go-live of the new quote tool.
Metadata to collect from the revenue operations head:
- Approval matrix history: which thresholds and routes applied in which years. Without it, nobody can tell whether an approval was required or optional.
- Quote and approval coverage: roughly how many nonstandard quotes per year, and whether recalled and resubmitted quotes keep their earlier steps.
- Field history settings: which quote and opportunity fields are tracked, and whether Field Audit Trail or an archive extends the window.
- Contract tool coverage: how many years of redlines the contract lifecycle tool holds, and whether drafts survive once an agreement is signed.
- Order coverage: how far back executed orders go in billing or ERP, and whether older orders were imported as summaries.
- Real deadline: when the old CPQ objects, package license or sandbox copies are retired.
- Authority and limits: who decides what is kept, and whether customer agreements restrict reuse of their terms.
Do not recommend keeping records beyond what the company's policies and customer agreements allow, and do not export anything yourself. The Salesforce archiving guide and the SaaS export rights guide cover the platform and contract side of keeping data out of a retiring tool.
SalesforceWhy approval history is the part a CPQ migration leaves behind
Migration plans move what the new tool needs on day one: products, price books, active contracts and open quotes. Closed quotes, and the approval steps attached to them, are history, and history is usually the last line of the scope document.
Three platform details make this concrete on Salesforce-based quoting, which many RevOps consultants will meet:
- Approval steps belong to the approval process. Salesforce's ProcessInstanceHistory is a read-only object that shows all steps and pending approval requests associated with an approval process. If the quote records those steps describe are retired or replaced, ask the company how the steps will stay readable, and by whom.
- Field history has a standard window. Without Field Audit Trail, Salesforce keeps field history for up to 18 months, and up to 24 months through the API. A discount that was changed three times in 2021 may already show only its final value.
- Longer retention is a setting, not a default. Field Audit Trail archives field history in a separate object, under a retention policy the company sets. Whether it was ever switched on is a one-line answer worth recording.
None of this says what any given company has kept. It tells you which questions turn a vague "we have years of deals" into an inventory a decision-maker can act on.
An illustrative inventory sheet
Illustrative only; the company and figures are fictional. A 410-person B2B payments software company is replacing its CPQ package within the year. The revenue operations head completes the sheet in one meeting from the migration plan, without opening a single quote.
| Record class | System | Years held | Owner | Moves to the new tool? | Readable until |
|---|---|---|---|---|---|
| Approval matrix versions | Policy documents, deal desk wiki | 2019 to now | Deal desk lead | Not needed by the tool | Kept on the wiki |
| Quote approval steps | Old CPQ objects in the CRM | 2019 to now | Revenue operations head | Open quotes only | Old CPQ package removal |
| Discount and term field history | CRM field history | Last 18 months | CRM administrator | No | Rolling window |
| Contract redlines | Contract lifecycle tool | 2020 to now | Legal operations | Not affected | Contract tool kept |
| Executed orders | Billing system | 2019 to now | Finance systems | Not affected | Billing system kept |
Reading the sheet: the contract and order history is safe because those systems are not changing. The approval steps, which are the record of who said yes to what, sit on the objects being retired, and the field history is shrinking every month regardless of the project.
Which date is the real deadline?
There are usually two, and neither is the go-live. The first is the date the old CPQ package, its objects or its last sandbox copy are removed. The second is a rolling one: every month, another month of discount and term changes falls out of the standard field history window unless the company has extended it. If the migration plan does not name a removal date, record that no date is set; do not invent urgency to fill the gap.
Who can authorize the discussion, and what stays unknown?
The revenue operations head knows where the records sit; the CEO decides whether licensing them fits the business, usually with the CFO or COO preparing the case, and the general counsel checks customer agreements. For board questions, see whether licensing data requires board approval and board approval for a data licensing agreement. Admin rights to the CRM are not authority.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
Until SourceX reviews the opportunity, nobody knows whether there is dataset demand for these records, what rights review will conclude, what must be removed or de-identified, or what the company would be offered. SourceX licenses approved business data directly from companies for AI training and evaluation and manages agreement, rights review, data preparation, delivery and payout. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. Other sectors are on the industries hub, and RevOps-specific guidance is on the RevOps consultants page.
Go deeper on nonstandard contract approval
- Nonstandard contract approval exception examples: one worked hard case, step by step, showing which record captured each approval decision.
- Nonstandard contract approval records across systems: a system map of the identifiers that join quote, contract and order records.
- Nonstandard contract approval referral brief template: a fill-in, metadata-only brief for writing the company introduction.
- Who can license nonstandard contract approval records: a decision tree for deal desk, legal and finance authority, and who can say yes to a licensing discussion.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the approval trail still joins up and the old CPQ objects have a removal date, register as a partner, check the company against who qualifies, and read the program terms and reward rules before you send the brief.