MIGRATION AND MODERNIZATION AT SCALE · ERP AND CRM

Migrate what you built on SAP, Salesforce or Dynamics 365.Your core stays.

Z developments, extensions, apps and reports built on top of SAP, Salesforce, Dynamics 365, Oracle, ServiceNow or Magento: we take them out and move them to own code, to your data platform or to your dashboards. The core of your system stays and is used through the API.

End 2027SAP ECCFewer per-user licencesParity measured piece by piece

Request a demo

Automatic demonstration · Tap your system and see what comes out from around its core and where it goes.

Migrating what surrounds your ERP and your CRM:the clock and the bill

Your ERP or your CRM is not migrated: the core of your system stays. What is migrated is what you have built on top of it, and before doing so it pays to know two things: when the system stops being supported and what the things built on top of it cost you every year. In ERP and CRM, the second one almost always weighs more.

End of support

Only SAP ECC has a date. The rest has a bill.

SAP ECC: standard maintenance until the end of 2027, extendable to 2030 for an extra fee. If SAP or your partner converts you to S/4HANA, the Z layer does not come along (clean core): it has to be emptied first.
Salesforce, Dynamics 365 and ServiceNow do not expire: they are SaaS. Their clock is the yearly renewal of the contract and the seats.
Oracle EBS and Adobe Commerce are still supported, but each version has its own date and each version jump drags the custom code along.

What you pay

The expensive part is not the core: it is what surrounds it

Per-user licences for people who only open a screen, a portal or a report built on top of the system.
Power Apps users, ServiceNow fulfiller licences, SAP BTP credits, the Adobe Commerce edition: fees that come from your extensions, not from the core.
The team that maintains the Z objects, the Apex and the plugins, and that has to touch everything again with every vendor release.

What staysand what goes

The core of your system stays: accounting, orders, the CMDB, the catalogue, the standard CRM that is actually used. It stays where it is and is accessed through the API.

We neither implement a new core nor migrate the one you have: the core of SAP, Salesforce, Dynamics 365, Oracle or ServiceNow stays, with its data. What we migrate is what has been built around it, and its data with it if needed.

What you built on top goes: Z transactions and apps, extensions, Apex and Flows, Power Apps and plugins, business rules and portals, custom modules, and the reports each of them carries.

And what nobody uses is switched off, without migrating it. The inventory says so before a single line is written.

Where what goes out ends up:you choose the destination

Each piece has one or two possible destinations. None of them ties you to another vendor unless you want it.

Own code

Java, .NET, Python or TypeScript, against the core’s APIs

Apps, portals, validations and integrations as own services that talk to SAP through OData, BAPI or IDoc, to Dataverse, to ServiceNow’s Table API or to Oracle’s REST. No per-user licence for what is yours.

Data platform

Databricks, Snowflake or Microsoft Fabric

ABAP batch jobs, PL/SQL extractions and heavy calculations leave the ERP and run on your data platform, with parity measured against today’s result.

Dashboards and analytics

Power BI, Tableau or Qlik Sense, or a custom dashboard

ABAP, X++, Salesforce, Reports and BI Publisher reports are moved to the tool you already have or, if you want to get rid of it, to own code on the data platform.

The vendor’s version, if you choose it

SAP implements S/4HANA and BTP; Magento Open Source keeps your code

If you are moving to S/4HANA, SAP or your SAP partner does the conversion. We empty the Z layer beforehand so that you arrive with a clean core and without having to take to BTP everything that is not clean core. BTP is a compared option: it also charges, in credits. In commerce, the same code keeps running on Magento Open Source or Mage-OS without the edition licence.

How to migrate what is built on an ERP or a CRMin four steps, without stopping the core

1Inventory of what is built on topWith read-only access: Z objects, extensions, Apex, Power Apps, business rules, modules and reports. What there is, who uses it and which core data it depends on.
2It stays, it goes or it is switched offEach piece with its verdict and its destination, and the cut-over plan piece by piece. What is not used is not migrated: it is switched off.
3Rebuild with your orchestrated AIDevelopment instances that rewrite, test and document each piece with the same method, against the core’s APIs. Your team decides and validates.
4Cut-over with measured parityEach piece is switched when the new one gives the same result as the old one with your real data. No big bang and no stopping the ERP or the CRM.

The rules

No new core and no core migration
What nobody uses is not migrated
Piece by piece, no single cut-over
You choose the destination

System by system:what goes out from around it and where it ends up

One summary per system. In the chart above you have each piece and its path: tap the system or follow the link.

End 2027before S/4HANA

Migrating what is built on SAP ECCwithout taking to BTP everything that is not clean core

The core stays: FI, CO, MM and SD; SAP or your partner does the conversion to S/4HANA. Ours are the Z objects and the extensions: they do not go into S/4, and they do not all have to end up in BTP paying credits.

What goes out

Z transactions and apps, exits and BAdIs → own app that talks to SAP through OData, BAPI or IDoc
ABAP batch jobs and reports → data platform and dashboards
Side-by-side extensions → SAP BTP if you want it, or own code with no credits

See the paths for SAP ECC

Per-user licence

Migrating what is built on Salesforcefewer licences, the same CRM

The standard CRM is still Salesforce, through the API. What goes out is what was implemented on top of its core, and with it who needs a licence to use it.

What goes out

Apex, Flows and custom screens → own code, with no per-user licence for what is built on top
Reports and formulas → Power BI, Tableau or Qlik Sense, or a custom dashboard
Whoever only looked at a report or a portal no longer needs a licence

See the paths for Salesforce

Dataverse · Finance & Operations

Migrating what is built on Dynamics 365Power Apps and X++ outside the core

The core stays, Dataverse and Finance & Operations, accessed through the OData Web API.

What goes out

Power Apps and C# plugins → own apps against Dataverse; the Power Apps licence goes away
X++ integrations → own services against the data entities
X++ reports → dashboards or own code

See the paths for Dynamics 365

PL/SQL · Forms

Migrating what is built on Oracle EBS and Fusionthe custom code out of the ledger

The ledger stays, through its open interfaces, PL/SQL and REST. What gets modernised is what has been stuck on around it over the years.

What goes out

Forms and custom interfaces → own pipeline that writes to the open interface
PL/SQL extractions → data platform, same output on the same accounting close
Reports and BI Publisher → dashboards or own code

See the paths for Oracle

Fulfiller licence

Migrating what is built on ServiceNowportals and apps without a seat

The ITSM engine (incidents, changes, CMDB, SLA) is still ServiceNow, through the Table API. What goes out is what forces you to buy a licence for someone who only serves a portal.

What goes out

Portals, apps and business rules → own services against the Table API
Fulfiller licences for people who only serve a portal: they go away
Reports → dashboards or own code

See the paths for ServiceNow

Edition · modules

Migrating Adobe Commercefrom the paid edition to Magento Open Source

The catalogue, the orders and the integrations with the ERP and the PIM stay. The shop does not stop: it is switched piece by piece.

What goes out

Adobe Commerce edition → Magento Open Source or Mage-OS: the licence goes away and the code keeps running
Custom modules, plugins and observers → out of process, as own services
Reports → dashboards or own code

See the paths for Magento

Frequently asked questions about ERP and CRM

Does migrating SAP ECC to S/4HANA force you to move the Z developments to BTP?

No. SAP or your SAP partner does the conversion to S/4HANA, and in S/4 (clean core) the Z objects do not come along. We empty the Z layer beforehand: each piece goes to own code, to your data platform or to your dashboards, and to BTP only if you choose it, because BTP also charges, in credits.

Can you cut Salesforce licences without leaving Salesforce?

Yes. The standard CRM is still Salesforce, through the API. What goes out is what was implemented on top of its core (Apex, Flows, custom screens and reports), and with it who needs a licence: whoever only looked at a report or a portal no longer needs one.

When does SAP ECC support end?

Standard maintenance for SAP ECC ends at the end of 2027, extendable to 2030 for an extra fee. Salesforce, Dynamics 365 and ServiceNow do not expire: they are SaaS and their clock is the yearly renewal of the contract.

Do you migrate the core of my ERP or my CRM, or its data?

No. We neither implement a new core nor migrate the one you have: the core of SAP, Salesforce, Dynamics 365, Oracle or ServiceNow stays, with its data. What we migrate is what has been built around it, and its data with it if needed, with parity measured piece by piece.

What have you built on your ERP or your CRM,and what does it cost you every year?

In a demo we show you the whole journey on a sample ERP: the inventory of what is built on top, what stays, what goes, where it ends up and how parity is measured. So that you can see what it would look like with yours.

Request a demo See the four scopes

We also migrate: Data integration and platforms · Dashboards and analytics · Code and applications · systems migration