Fit
When this is your problem
"The blueprint says one thing. The floor does another."
"Roles and profiles for the new system are a guess."
"Our documentation is years behind reality."
"Consultants interviewed the leaders, not the users."
Proof
Edenor mapped 900 people in 2 waves ahead of its SAP S/4HANA migration, with a 9.1/10 pilot satisfaction score.
The pilot covered HR and Information Security (89 people), rebuilt job descriptions from real activity, and defined role-based security profiles from what people actually do.
9.1/10pilot satisfaction, Edenor
Method
How Horizon does it
- 01
Horizon interviews the users who run the current systems, ~25-35 minutes each.
- 02
Horizon maps current processes to BPMN and runs gap-fit against the to-be design.
- 03
Horizon delivers roles, transactions, and security profiles from real activity, plus post-go-live monitoring.
Outcomes
What you get
- Current processes mapped to BPMN, fast
- Gap-fit analysis against the to-be design
- Roles, transactions, and security profiles from real activity
- Adoption and compliance monitoring after go-live
FAQ
System Migration on a process intelligence platform
Why do so many ERP migrations fail?
Because the blueprint is built on documentation that has drifted from reality. Horizon maps how work actually happens before the move, so the gap surfaces before it bites, not after go-live.
Can Horizon define security roles for the new system?
Yes. Horizon derives roles, transactions, and security profiles from real activity, instead of guessing.
Does it work for CRM and WMS too, or only ERP?
It works for ERP, CRM, and WMS migrations, any move where the as-is needs to be true before the to-be is designed.
Pick a use case. We'll prove it in a week.
Horizon is an enterprise intelligence platform, a new category of process intelligence, that turns what your people know into evidence, hours, and initiatives.