Journeys Through Search

Salesforce CPQ data migrationQuotes, contracts and subscriptions that renew and amend correctly.

CPQ data is not like contacts. Quote lines depend on products and price books, subscriptions depend on contracts, and renewals depend on all of it. Load it in the wrong order or skip a link and the next amendment comes out wrong. Here is how a CPQ data migration works and the order it runs in.

  • Catalog first, then quotes, then contracts and subscriptions
  • CPQ triggers paused for the load, quotes recalculated after
  • Legacy quote and contract data mapped to CPQ objects

900+ integrations completed · Salesforce partner · We sign BAAs

Salesforce CPQ data migration order

  1. 1
    Catalog

    Products, price books, price book entries, then bundles, options and rules

  2. 2
    Quotes

    Accounts and opportunities, then quotes, quote line groups and quote lines

  3. 3
    Contracts

    Contracts, then subscriptions and assets tied to them

How a Salesforce CPQ legacy data migration works

Salesforce CPQ adds its own objects on top of the standard ones. Products and price books are standard; product features, product options, price rules and product rules are CPQ configuration; quotes and quote lines are CPQ records that hang off opportunities; subscriptions and assets hang off contracts. Each layer needs the one before it.

So the catalog goes first: products, the standard and custom price books, and a price book entry for every product in every price book it sells in. Then bundles, with their features and options, and the price and product rules that drive configuration. Then accounts and opportunities, followed by quotes, quote line groups and quote lines, with bundle children pointing to their parent line.

Contracts come next, then subscriptions and assets for what the customer owns, with quantities, prices and start and end dates. These are what CPQ reads when it builds a renewal or an amendment, so they are checked line by line against the legacy system.

CPQ runs its own calculations and triggers when quotes and lines are written. The CPQ package has a setting to turn those triggers off, so legacy prices load as they were. After the load, triggers go back on and quotes are recalculated and compared, so any difference is found before a rep finds it.

What's included

What Salesforce CPQ data migration includes

Catalog load

Products, price books and price book entries, with the old product codes kept as External IDs.

Bundles and rules

Product features, options, price rules and product rules loaded and tested on a sample quote.

Quotes and quote lines

Quotes tied to the right opportunity, the primary quote marked, and lines tied to the right product and parent bundle line.

Contracts and subscriptions

Contracts with their dates and terms, and subscriptions and assets for every product the customer holds.

Legacy pricing kept

Discounts and negotiated prices loaded as they were, with CPQ triggers paused so they are not recalculated on the way in.

Renewal and amendment check

Sample contracts amended and renewed in the sandbox to prove the subscription data is complete.

What to leave behind

Expired quotes and dead deals can stay in an archive or come over as plain records, so CPQ only carries what it needs.

Built with your CPQ setup

Where CPQ is being set up at the same time, the catalog and rules are built to fit the data coming in.

Works with

All Salesforce integrations

Every system we connect to Salesforce, in one list

Call tracking

CallRail and CallTrackingMetrics native integrations, with recordings and AI call summaries on the lead

Web forms

Gravity Forms, Jotform and Typeform fills create leads with tracking attached

Chat and texting

LiveChat, SnapEngage, Tawk.to and Avochato conversations saved to the lead

EMR

Kipu and Sunwave: admissions in Salesforce, clinical in the EMR, kept in step

Billing and financial

CollaborateMD, AdvancedMD and HiLite, with insurance payments on the patient

Payments

Stripe, PayTrace and PayPal payments recorded on the opportunity

Ad platforms

Google Ads, Microsoft Ads, Meta and TikTok leads in, offline conversions out

Email marketing

ActiveCampaign lists and automations that follow Salesforce

Single sign-on

Open other systems from the Salesforce record with SSO

Reporting

Salesforce data in Google Sheets, BigQuery and Looker Studio

Anything with an API

No app for it? We build the connection with Apex and the APIs

Moving quote and contract data into Salesforce CPQ?

Book a free call. We look at your catalog, your quotes and your contracts, and tell you how they should land in CPQ. No obligation.

Book a free call →

What clients say

900+ integrations completed
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
Jason Landver
CEO, Recovery Beach
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
Mike Kwak
On-Site Adjusting
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
Tarra Boggs
EHS & Compliance Operations Manager

How it works

How Salesforce CPQ data migration works

  1. 01

    Free call

    Your legacy quoting data, your CPQ setup and what has to renew or amend after go-live.

  2. 02

    Project quote

    Priced by project, not by the hour. You approve before we start.

  3. 03

    Map and test

    Every CPQ object mapped, then loaded into a sandbox with renewals and amendments tested.

  4. 04

    Load and recalculate

    Production loaded in order, triggers back on, quotes recalculated and compared.

Working with us

Salesforce CPQ data migration FAQ

What is the Salesforce CPQ data migration order?

Products, price books and price book entries; then bundles, options and rules; then accounts and opportunities; then quotes, quote line groups and quote lines; then contracts, subscriptions and assets.

Will CPQ recalculate our legacy prices?

Not during the load. The CPQ package lets you turn its triggers off, so prices load as they were. After the load we turn them on, recalculate, and compare.

Why do subscriptions matter so much?

CPQ builds renewals and amendments from subscriptions on the contract. If a subscription is missing or has the wrong dates, the next renewal is wrong.

Do all old quotes have to come over?

No. Open quotes and those tied to active contracts matter to CPQ. Older ones can stay in an archive or load as plain history.

Do you set up CPQ too?

Yes. See Salesforce CPQ implementation. The catalog and rules can be built and the data loaded as one project.

How is it priced?

By project, not by the hour. The first call is free, and you get a project quote after it.

Related