Oakline Manufacturing: moving from Anaplan without losing a number
Oakline Manufacturing is a fictional industrial company moving its planning from Anaplan to Pigment. A straight copy would have carried over years of workarounds. This blueprint maps, redesigns and runs both models side by side until every total ties.
Blueprint: this model is fully designed and documented, and the live demo is being built next. The company and figures are fictional.
The problem
What wasn't working
The Anaplan model had grown over six years, with helper modules, duplicated lists and logic nobody could explain. The team wanted Pigment's flexibility without rebuilding everything blind.
The design
How the model is built
- Inventory every module, list and line item, and tag each as keep, redesign or retire.
- Map Anaplan concepts to Pigment: lists to dimensions, modules and line items to metrics, saved views to views and boards.
- Redesign where Pigment does it better, such as versions, scenarios and access rights, instead of copying workarounds.
- Run both models for one full planning cycle, with reconciliation metrics comparing every key total.
Inside the model
What planners work with
Mapping register
A live register of every Anaplan object, its Pigment equivalent, owner and status.
Reconciliation
Side-by-side totals by version, entity and month, with differences flagged until they reach zero.
Cutover plan
Data loads, user training and a freeze window, rehearsed before the real switch.
Documentation
Each Pigment block documented with its Anaplan origin, so the team can trace any number.
Decisions that matter
Why it holds up
Redesign, don't transliterate
Workarounds built for Anaplan's limits are retired, not copied.
Parallel run is mandatory
No cutover until one full cycle ties in both models.
Traceability
Every Pigment block links back to its Anaplan source for audit and training.
What the client gets
A cleaner Pigment model, proof that every number ties to the old system, and a team trained to own it from day one.
More work
Other projects
SaaS FP&A on a hub-and-spoke
ARR engine, three versions, five cases and a write-back reforecast workbench across three Pigment applications.
Position-based workforce planning
Headcount roll-forward with hires, leavers and transfers, a merit cycle and fully loaded cost feeding the P&L.
Territory and quota planning
Account scoring, balanced territories, ramped rep capacity and quota set top-down against bottom-up capacity.