About SEN

Universal ERP migration

SEN started as an SAP-to-SAP migration tool. It has evolved into a universal ERP displacement platform that migrates any source system -- SAP ECC, Infor LN, M3, CloudSuite Industrial, Lawson -- to SAP S/4HANA through a canonical data model.

The canonical model is the key insight: 14 OAGIS-aligned entities that serve as a universal translator. When a new source ERP is added, only the source adapter needs to be written. Every existing migration object, validation rule, and industry compliance check works automatically. This is N+M scaling, not N x M.

Why SEN exists

ERP migrations take 6 to 48 months, involve dozens of consultants, and cost millions of dollars. The majority of that time goes toward repetitive manual tasks: scanning custom code, profiling data, mapping fields between systems, and testing transforms.

SEN automates these tasks. Instead of spreadsheets and consultant guesswork, it provides a programmatic framework that forensically extracts, canonically maps, transforms, loads, validates, and tests -- all through code that can be version-controlled and reproduced.

The goal is not to replace consultants. It is to eliminate the repetitive parts of their work so they can focus on business process design and the decisions that require human judgment.

By the numbers

Open source philosophy

Every line of code is visible. Every migration rule, every transformation, every validation check can be inspected and audited. There are no black boxes.

ERP migration knowledge should not be locked behind proprietary tools. By building in the open, we enable the community to contribute extractors, fix rules, and share patterns that benefit everyone.

Technology foundation

Built on Node.js, SEN connects to SAP through three protocols: RFC for direct ABAP function calls, OData V2/V4 for service-based access, and ADT REST for development tool operations. Infor connectivity uses ION API Gateway, M3 MI Programs, IDO REST, and Landmark REST.

The platform runs as two servers: a CAP server on port 4004 for OData services and Fiori interfaces, and an Express server on port 4005 for REST APIs.