CRM Line-Item Migration: Reconcile Products and Totals

Published on
Last updated
Reading time7 min read
CRM Line-Item Migration: Reconcile Products and Totals

CRM line-item migration is complete when each deal retains its agreed products, quantities, prices, discounts, and billing terms. Reconcile those fields individually, then compare the calculated totals and the CRM's stored deal amount. A matching revenue total can hide the wrong commercial agreement.

In our executed three-line example, three deliberately broken imports preserved both the row count and every deal's calculated total. One changed quantities, another changed the product, and the third changed a billing period. This guide gives CRM administrators a practical acceptance plan; use the broader CRM migration checklist to coordinate the cutover.

Define the CRM line-item migration contract

Separate the product catalog from the products sold on a deal. The catalog describes what you sell today. A deal's line item records what a particular buyer agreed to purchase. Rebuilding old sales from current catalog prices can overwrite a negotiated price or an earlier package definition.

Keep three identities: the product, the deal, and the line item joining them. Two lines can reference the same product but have different start dates, discounts, or service descriptions. Combining them because their product IDs match destroys that distinction.

Field groupPreserveAcceptance question
IdentitySource line, deal, and product IDsIs this the same commercial row?
QuantityNumber and selling unitSeats, hours, packs, or another unit?
PricingAgreed unit price and currencyDid the historical price survive?
DiscountsType, value, and scopePercentage, per unit, or whole line?
BillingFrequency, start, and termWhat does this amount buy?
AmountsLine net and stored deal amountDo both follow the agreed rules?

Add tax treatment, quote version, and product variation when the sales process uses them. Record intentional exclusions before calculating expected totals. A retired catalog product can still belong on a historical deal; removing it from the active catalog does not justify dropping the sale.

Use the CRM requirements checklist to decide which fields the destination must represent. If a required billing term has nowhere to go, resolve that model before the import rather than burying the term in an unsearchable note.

Map products and deals before loading lines

Build separate ID crosswalks for deals and products, then give each migrated line a stable source identifier. Keep a repair ledger linking that identifier to the destination line ID. Product names are review labels: a renamed subscription should still map to the intended product, while two packages sharing a display name should remain distinct.

Import the catalog and deals before creating their transaction rows. Check that each line resolves to exactly one destination deal and the intended product or approved custom-item representation. Quarantine unresolved references instead of silently creating another product from the line's display name.

Pipedrive's product documentation states that imported products are not automatically linked to deals. Its documented routes for attaching them are manual linking or the API. A successful catalog import therefore leaves a separate deal-product job to complete.

Use CRM association migration checks for the relationship model and CRM export completeness for the source package. The product count, line count, and deal count answer different questions. Save all three counts, but require each imported line to resolve through the crosswalk as well.

When comparing Pipedrive and HubSpot, include your actual product-to-deal import route in the evaluation. Ask for a demonstration with two lines for the same product and different commercial terms, rather than approving the process from a clean catalog upload.

Preserve negotiated prices and discount meaning

Use the source deal's agreed unit price as the historical input. Do not fetch a fresh catalog price during migration unless the business has explicitly decided to reprice those deals. Preserve the original currency alongside the price and quantity.

Pipedrive's deal-product instructions explain that a price customized while attaching a product applies to that deal without changing the catalog price. That distinction belongs in the export and mapping specification: a catalog-only price file cannot reconstruct every negotiated deal.

A discount field also needs a unit. Ten percent and ten dollars are different operations. A fixed discount per unit and a fixed discount across the entire line are different again. Store the type and scope with the value; do not infer them from a column called discount.

For example, three units at $100 with a 10% discount produce a $270 line net. A $10 discount on the whole line produces $290. A $10 discount per unit produces $270, matching the first total while preserving a different pricing rule. That difference matters when someone changes the quantity later.

Write the calculation order in the acceptance contract. Decide when discounts apply, whether prices include tax, and where rounding happens. Use decimal arithmetic for the rehearsal so a representation error does not become a supposed commercial adjustment. For multi-currency deals, carry the decisions from CRM currency migration into this calculation.

Keep billing periods out of ambiguous totals

A monthly price, annual contract value, and one-time setup charge can appear together on a deal. Name the amount being reconciled. Summing one period of each line is a different calculation from annual recurring revenue or total contract value.

Keep billing frequency, number of periods, and start dates separate from the amount. If the destination transforms them, specify the transformation and compare its result explicitly. A $100 monthly row becoming $100 yearly can leave a simple line-net check unchanged while altering the contract.

Use the sales forecasting methods guide to identify which downstream reports consume the migrated amount. Decide whether each report should use recurring revenue, contract value, or a manually agreed opportunity amount before releasing it to the sales team.

Test CRM line-item migration beyond revenue totals

We created and ran a Python reconciliation exercise with three invented lines across two deals. Deal D1 contains three monthly seats at $100 with a 10% discount, plus two one-time setup units at $120. Deal D2 contains one monthly seat at $100. The expected one-period, pretax totals are $510 for D1 and $100 for D2.

The exercise uses decimal arithmetic and rounds each line to two decimal places with half-up rounding. Its fixed discount is applied to the extended line, and it does not annualize recurring rows. Download the Python exercise and executed results; run it with python3 crm-line-item-migration.py.

Import scenarioRow countPer-deal totalsExact fields
Correct importPassPassPass
Offset quantity changesPassPassFail
Wrong productPassPassFail
Monthly period becomes yearlyPassPassFail
Percentage becomes fixed line discountPassFailFail
Catalog price replaces agreed pricePassFailFail
Duplicate replaces another linePassFailFail
One line missingFailFailFail

The offset case changes D1's seat quantity from 3 to 4 and its setup quantity from 2 to 1.25. The seat net becomes $360 and the setup net becomes $150. The deal still totals $510. An amount-only reconciliation approves a materially different order.

All seven deliberately broken candidates failed exact comparison. Three passed both the count and per-deal total checks. The script preserves duplicate occurrences when comparing rows, so a duplicated line cannot disappear through set-based deduplication.

Use these results to design three acceptance layers: identity and field equality, calculated amounts, and stored deal amounts. Translate destination IDs back into source identities before comparing. Report missing, unexpected, duplicated, and changed lines separately so a repair can target the actual defect.

Define equality before reviewing exceptions

Normalize numeric formats such as 3 and 3.0 to the same decimal value. Normalize approved billing labels through a mapping table. Retain differences in quantity, currency, discount scope, and product identity. The fixture compares already normalized strings; production exports need that normalization step first.

Keep expected transformations separate from defects. If two source products intentionally become one destination product, record the mapping while preserving each line's source identity. If the business intentionally rounds a fractional quantity, approve the changed commercial amount and update the expected result before acceptance.

A tolerance should describe a specific rounding rule. Avoid a blanket percentage tolerance that could excuse a missing low-value product on a large deal. Inspect rounding differences per line and currency, then verify that the remaining deal-level difference is fully explained.

Reconcile stored deal amounts separately

A correct set of imported line items does not establish that the opportunity amount was recalculated. HubSpot's deal line-item documentation says importing line items or updating them through the API does not update the associated deal amount. Include that stored field in the acceptance report.

For every migrated deal, compare the expected commercial metric, the amount calculated from destination line data, and the amount stored on the deal. If the stored amount is intentionally manual, preserve that decision. Do not overwrite it merely to force equality with a different calculation.

Assign an owner for the deal amount through CRM field ownership. A connector that restores an old opportunity value after acceptance can undo the migration's result. Test one subsequent sync and confirm which system is permitted to write prices, quantities, and the headline amount.

Review HubSpot and Salesforce with these requirements in hand. Evaluate the actual destination behavior for the chosen import mechanism and amount definition, then include the result in the implementation acceptance criteria.

Release line items in controlled batches

Start the rehearsal with a normal deal, a negotiated-price deal, a fractional quantity, a repeated product, a recurring row, and an archived product. Include a discount and currency combination that has caused confusion in your own sales process. Save source rows and expected outputs together.

Run the import in dependency order, collect rejected rows, and reconcile the resulting lines before enabling quote generation or amount-based automation. Use the CRM sandbox refresh checklist to keep the rehearsal isolated from live integrations. Repeat the same checks on the final export after the write freeze.

Test a narrow replay before repairing a failed batch. Establish whether the importer updates a line by stable ID or creates another row. A second upload that duplicates the first batch can double revenue while still reporting a successful import job. Preserve the destination IDs needed for a targeted update.

Keep the source export, crosswalks, field mappings, arithmetic rules, import output, and exception decisions in the cutover package. The migration owner should approve resolved differences before quote creation and reporting resume. The CRM implementation checklist can carry those acceptance gates into the broader rollout.

When those products belong to renewable agreements, use CRM renewal migration to preserve contract dates and the customer success action queue.

Frequently Asked Questions

What is CRM line-item migration?

It is the transfer of a deal's individual product or service rows, including their quantities, agreed prices, discounts, currency, and billing terms. Moving the product catalog alone does not transfer those agreements.

Can deal totals match while line items are wrong?

Yes. Different quantity and price combinations can produce the same total. Product identity and billing-period changes can also leave an amount unchanged. Compare the individual fields and the calculated totals.

Should migrated lines use current catalog prices?

Preserve the price agreed on the source deal. Use current catalog prices only for an explicitly approved repricing operation. Keep the product reference and historical unit price as separate inputs.

What should happen before sales workflows restart?

Resolve product and deal mappings, reconcile line fields and amounts, check stored deal values, and test a subsequent integration sync. Repair exceptions through stable line IDs before releasing affected workflows.

Choose the destination around the commercial model

Give each shortlisted CRM the same small acceptance package: repeated products, negotiated prices, explicit discount scopes, and recurring terms. Require the proposed import route to preserve those fields and produce the agreed amounts.

Use Zoho CRM versus HubSpot for another destination comparison. Carry the resulting acceptance contract into the purchase and implementation plan so a successful import means the sales team can still understand what each customer agreed to buy.