Latest episode
Anaplan to OneStream migration once the statutory close has come into scope.
Constancia, an EPM consultancy, moves groups off Anaplan (planning software) onto OneStream (EPM software) when the statutory close joins the plan. The plan moves and the consolidation is designed, and the survey prices both.
OneStream at a glance
- Covers
- Planning, financial close and consolidation, reporting and analytics.
- Data in
- Direct integration to Oracle, SAP, Microsoft, IBM, Infor, Workday, Databricks and Snowflake.
- Our record
- 58 implementations over 35 years.
On the Anaplan route the plan moves and the close is designed, and the design sets the price.
An Anaplan to OneStream migration moves the planning model onto OneStream and designs the consolidation, for a group that wants both on 1 platform. The plan is the half that moves, and the close is the half that is built. A finance team on this route usually has an audit or an acquisition in the diary.
Anaplan describes its own product as "connected planning" on its website, and its models are built from lists, modules and line items. Constancia, an EPM consultancy, has completed 58 OneStream implementations over 35 years and prices this route after reading the model.
Where the group plans in Anaplan and closes in a workbook, budget and actuals meet in a third spreadsheet that maps 2 charts of accounts. The finance director reads a variance nobody can trace to a ledger. The mapping table in that spreadsheet is the first object the survey reads.
The Anaplan model crosses in 6 steps, with the consolidation designed between steps 2 and 3.
Each step names the object it moves or builds. The close is read before the dimensions are designed, because the plan has to share them with it.
- 01
Read the model
We list every list, module and line item in the Anaplan model, with the dashboards and imports that use each.
- 02
Read the close as it runs
The consolidation, wherever it runs today, is read entity by entity, because it has to share dimensions with the plan.
- 03
Design the shared dimensions
Entities, accounts, periods and the drivers the plan needs are designed once, for the plan and the close together.
- 04
Rebuild the plan
The modules and line items become OneStream cube views, forms and rules on the shared dimensions, each traced to its Anaplan source.
- 05
Build the consolidation
Ownership, currency translation and eliminations are built as OneStream rules and tied to the current close, period by period.
- 06
Run the plan cycle twice
Anaplan and OneStream produce the same forecast until the outputs agree, and the close runs in parallel with the old one.
The drivers keep their owners outside finance on the move, because a driver with no owner is an assumption on a new system too.
Anaplan objects go 3 ways, with the close arriving as new design beside them.
The survey puts each object in the Anaplan model into 1 of 3 columns. The consolidation appears in none of them, because it is designed on OneStream from the current close.
| Maps directly | Is rebuilt | Is dropped | |
|---|---|---|---|
| Lists | Entities, cost centres and products in use. | Lists that hold 2 kinds of member, split into 2 dimensions. | Numbered lists left from a retired model. |
| Modules | Driver input modules with 1 owner each. | Calculation modules, as OneStream rules on the shared dimensions. | Staging modules that moved data between other modules. |
| Line items | Inputs and simple roll-ups. | Formulas with a chain of 5 or more dependencies, rewritten and documented. | Line items no dashboard or export reads. |
| Imports and exports | Ledger imports with a 1 to 1 mapping. | Imports that reshape the file first, as OneStream data sources. | The export to the consolidation workbook. |
| Dashboards | Standard management views. | Board dashboards, rebuilt on the plan and the actuals together. | Personal dashboards of people who have left. |
| Versions and history | Actuals and the signed budget. | Forecast versions, restated onto the shared dimensions. | Scratch versions from old planning rounds. |
A date sits in each of the 4 situations that lead to the Anaplan route.
- 01
The close has come into scope
An audit, an IPO or an acquisition has put the statutory consolidation on the finance team's desk, beside the plan.
- 02
2 platforms and 1 team
The finance team maintains a planning model and a separate consolidation, and wants to run 1 system.
- 03
A variance that needs a mapping
Budget and actuals live on 2 charts of accounts, and every variance report starts with a mapping table.
- 04
Drivers that already have owners
The pipeline, headcount and volume drivers in the Anaplan model have named owners, and they move with it.
A group whose consolidation is settled and whose plan is not reads about Abacum (FP&A software) instead.
4 more routes into OneStream cover HFM, BPC, FCCS and TM1.
Hyperion to OneStream
HFM's hierarchies are the object that moves, and the history follows them.
Read the Hyperion routeSAP BPC to OneStream
The BPC route separates a plan and a close that share 1 script logic file.
Read the BPC routeFCCS to OneStream
The FCCS route removes the exchange jobs between Oracle's applications.
Read the FCCS routeTM1 to OneStream
The TM1 route ends with a plan whose every rule has a traced source.
Read the TM1 route
See more on our
Subscribe on YouTube
Every Sunday, 6am
The Sunday Close.
Our weekly newsletter on AI in finance.
Yours to enjoy with your Sunday morning coffee.
- AI in finance observations from Alex (CEO) and Brad (COO)
- Newest video from our YouTube channel
- AI in finance trends we have spotted each week
Tell us the date you are working to.
The people who would do the work read every message and reply inside 2 working days.