From Excel to Revenue Cloud: getting your quotes out of the spreadsheet

The Excel quoting file is the most profitable and the most dangerous tool in your company. Profitable, because it made it possible to sell without a process for years. Dangerous, because it has no controls, no history and no scalability - and it retires with the person who masters it. Here is how to get out of it methodically.

01What the spreadsheet really costs you

• Wrong prices - multiple versions of the file, broken formulas, improvised discounts: the error goes out to the customer, signed.
• Zero visibility - impossible to know which quotes went out, at what price, with what margin, without consolidating by hand.
• Non-transferable knowledge - the day "the person who owns the file" leaves, your pricing leaves with them.
• Permanent reconciliation - the quote in Excel, the order in the ERP, the invoice somewhere else: three truths, none reliable.

02The method: migrate the rules, not the file

The classic mistake is trying to reproduce the spreadsheet in the tool. The spreadsheet is not your pricing: it is the archaeology of your pricing. The approach that works:

• Extract the living rules. Of the file's 300 lines, how many are still used? We start from the last 18 months of sales, not the full history.
• Simplify the catalog. It is now or never: products, bundles, options - we only migrate what sells.
• Model natively in Revenue Cloud: pricing procedures, tiered discount grids, manual discounts subject to approval (native workflows, sequential or parallel, built on Flow Orchestration). What used to be an Excel formula becomes a controlled, traceable rule.
• Run in parallel for one cycle: a representative set of quotes goes through both systems, we compare the pricing waterfalls line by line, adjust, then switch over. Salesforce itself recommends redesigning your processes rather than replicating the existing ones.

You don't migrate a spreadsheet. You migrate the knowledge it contains - and throw away the rest.

03What the spreadsheet becomes, concretely

• A stable rate card becomes a Decision Matrix - imported from a CSV, versioned with dates and priorities; an active version can no longer be modified, you create a new one. No more "H1 / H2" tabs.
• Tabs per period become effective dates - each price carries a validity start and end; two grids coexist in the database, and the right one is picked at the transaction date. Mass revisions are done in batches, with a revision policy (formula or index).
• The grid is normalized before it goes in - volume tiers cannot overlap, and in attribute-based pricing, each rule must cover all the attributes that influence the price: a grid with variable granularity requires an explicit "none" value where Excel left a blank cell.
• Acceptance testing becomes a simulation - the simulator shows the pricing waterfall step by step; you validate a quote before activating the rule, not after the customer complains.

04The pitfalls that make it fail

• Wanting to cover everything on day 1. The 5% of edge cases can stay manual for three more months; blocking the project for them costs more than handling them separately.
• Forgetting the sales reps. If they find the tool slower than their file, they will keep the file. Our rule: a standard quote must go out in under 5 minutes, otherwise it is lost.
• Discovering finance at acceptance testing. Revenue recognition, amendments, renewals: to be simulated before go-live, not after.
• Forgetting to synchronize. Operational trap number 1: after any price change, the pricing data and decision tables have to be resynchronized - otherwise "I changed the price but nothing happens".
• Neglecting the takeover of work in progress - open quotes, active contracts: without a takeover plan, you run two systems for a long time.

05The first step

Send us your quoting file (yes, the real one): in one scoping workshop, we tell you what can be modeled in standard, what deserves a specific rule, and what should disappear. Our Revenue Cloud expertise - or a conversation, directly.