Latest episode
Legacy EPM migration to OneStream from HFM, BPC, FCCS, TM1 or Anaplan.
Constancia, an EPM consultancy, moves multi-entity groups off 5 source systems onto OneStream (EPM software). We read what the old system will release before we price the route.
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.
A legacy EPM migration moves 3 things, and the source system decides how each one moves.
A legacy EPM migration moves a group's consolidation, plan and history off 1 source system onto the platform it will run next. The finance team doing it usually has a date already set by the support timetable on its current release.
Constancia has completed 58 OneStream implementations over 35 years, as an official partner of OneStream with certified consultants based in the UK. The route off each source system is priced after we have read that system.
Where the source holds history at group level and the ledgers post at account level, the history is rebuilt at the lower grain first. A comparison between the 2 systems ties out after that step and never before it.
The object that moves first is different on each of the 5 routes to OneStream.
Each source system holds its logic in a different place. The survey on every route starts with that place, and the table names it.
| The object that moves | What the survey reads first | |
|---|---|---|
| Hyperion (HFM) | The account, entity and custom hierarchies, with the consolidation rules attached to them. | Each hierarchy's purpose, member by member, because a mature HFM dimension carries years of restructuring. |
| SAP BPC | A consolidation and a plan that share 1 model and, often, 1 set of script logic. | Which lines of the logic serve the plan and which serve the close, so the 2 can be separated in the design. |
| Oracle FCCS | A cloud consolidation that sits beside separate Oracle applications for planning and reporting. | How the separate applications exchange data today, because on OneStream that exchange becomes 1 model. |
| IBM TM1 | Cubes, the rules files attached to each cube and the TurboIntegrator processes that load them. | Every rule, sorted into kept, rewritten or dropped, before the first cube is rebuilt. |
| Anaplan | A planning model built from lists, modules and line items, with the close elsewhere. | Where the statutory close runs today, because the consolidation on this route is a design job. |
Every source system has its own route, priced after its own survey.
Hyperion to OneStream
The HFM hierarchies are rebuilt for what each one was for, and the history follows them.
Read the Hyperion routeSAP BPC to OneStream
The plan and the consolidation are separated in the design before either is built.
Read the BPC routeFCCS to OneStream
Separate Oracle applications come onto 1 model, and the group decides whether it wants that.
Read the FCCS routeTM1 to OneStream
Every rule in the cubes is read and sorted before the planning model is rebuilt.
Read the TM1 routeAnaplan to OneStream
The plan moves and the consolidation is designed, because the close ran in another system.
Read the Anaplan routeSpreadsheets to OneStream
With no source system, the whole model is a design job and the survey reads the workbooks.
Read about implementation
2 services follow a migration once the new close has tied out.
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.