SAPERP

SAP projects, taken all the way to go-live.

SAP rollouts fail on planning, not technology. We run the integration side as a project with dates, owners and a rehearsed cutover.

3SAP editions: Business One, ECC and S/4HANA
Day 1integration plan aligned to SAP Activate
Rehearsedcutover, before the weekend that counts
What we build on it

A plan before a single interface

Every interface on the landscape listed with its owner, direction and go-live date, aligned to the phases of your SAP Activate plan rather than run beside it.

The right interface for the edition

Service Layer and DI API on Business One; OData, BAPIs and IDocs on S/4HANA and ECC; SAP Integration Suite where the landscape already uses it.

Cutover rehearsed, not hoped for

Data loads and interface switch-overs run end to end in rehearsal before the weekend that counts, with a rollback plan and hypercare after go-live.

Something in SAP that will not reach the rest?

Tell us what is on each side and what has to move between them. Datsugi replies within 2 business hours, guaranteed (CET).

Arrigo Lupori

Arrigo Lupori

Founder & Managing Director

Get your free systems design session

Required
Required
Required