1. Along with implementing a brand new CQP/CLM system, turn your attention
to your legacy data. You will have to think about how and when you handle
legacy data after CPQ has been implemented.
Your legacy data could be:
• In paper files, emails or in other systems.
• It could be structured data as well as unstructured data.
• Even if it is structured data it still may not have all the relevant attributes.
Your legacy data would be critical for your business going forward:
• It will affect renewals, amendments for existing customers.
• Your existing customers expect negotiated customer prices and discounts.
• Your new product offerings may depend on the products and services that
the customer has already signed up. So need to know customers
inventory.
• To add to the complexity you may have just cleaned up the product
catalogue and product bundles for the new implementation. However, the
legacy data would still be carrying the old product offerings.
Sudhir Mahajan 1
2. Contract terms and conditions - NonStandard
Data Cleanup
Contracted Pricing
Negiotiated
Discount Net term
Products
Customer
data
Start
date
Sku 1Contract
Value &
Special Prices
PriceEnd
date
Terms Discount
Sku 2 Price Discount
Perp / Subscription/ Services Warranties Indemnity Liabilities
Map to Sku/Bundles & Data transformation
Contracted Pricing
& Negotiated
discounts
Customer
licensed Products
& Services
Opportunity
Assets/Subscr
iptions
Search
attributes
filters
Scan & OCR data Export data
Agreement
data
Account/Cu
stomer
data
Sudhir Mahajan 2
3. Data Map
Agreement
Agreement
Document
Agreement
LineItems
Account Opportunity Product
Price List Item
Price List
Quote
Proposal
Configuration
Account
Location
Configuration
LineItems
Proposal
LineItems
Contracted Pricing
& Negotiated
discounts
Current
Product
Configuration
Opportunit
y
data
SearchAgreement
data
Account
data
Sudhir Mahajan 3
4. Some of the major issues this process assumes and
addresses are:
• Legacy data is spread across enterprise in
different formats
• CPQ install lead to product catalogue cleanup and
therefore sku transformation is necessary
• It should be possible to renew legacy contracts
• Search process will be agnostic of new v/s legacy,
user always searches from a single screen
Sudhir Mahajan 4
