Implementation
Migrating Price Books: Version the Rules, Not Just the Rates
By the Orvlin team · · 1 min read
Price book migration: what to decide
Two prices both say $0.01, but one applies to each request and the other to each thousand requests. Copying values without units can create a thousandfold error. The migration needs rule-level comparisons.
Document each model and its boundaries before translating it. Include volume versus graduated behavior, minimums and rounding. Keep inactive historic versions available when corrections or old invoices need reproduction.
Follow one account through the calculation
A graduated offer bills the first 1,000 units at one rate and the remainder at another. Importing it as volume pricing applies the final tier rate to all units, changing the invoice even though the tier table looks identical.
Check this before launch
Do not let a platform’s default fill undefined fields without review. Default timezone, rounding or allowance resets may differ from what existing customers agreed to.
Steps to take next
- Inventory complete rating rules and units.
- Translate model semantics explicitly.
- Replay representative and boundary quantities.
- Preserve historical versions and customer exceptions.
Frequently asked questions
- Can we simplify old plans during migration?
- Only through an explicit commercial decision and any required customer agreement. A technical migration should not silently change negotiated economics.