Customer and process data stuck inside SAP, licences for touching your own data, and a migration clock ticking towards 2027. It can work differently: your data in an open data layer that's yours, alongside or instead of SAP. No data loss, no big bang, at your own pace.
SAP is solid and has been doing its job for finance and logistics for years. But the moment you want to do something with your own data outside SAP, a customer view, a report, an integration, an AI application, you find out who actually owns the data in practice.
Data in-house means: your customers, orders and process data in an open PostgreSQL database that's yours, on EU hosting that you control. SAP can simply keep running alongside it for finance and logistics, or be phased out over time, whenever you want.
A report, a field, an integration: every change is a ticket with the SAP partner, with the lead time and invoice that come with it.
Software that works with your SAP data through an integration can also be subject to licensing. You pay for touching your own data.
Regular maintenance on the old ECC generation winds down towards the end of 2027. Anyone still on it has to migrate regardless; the only question is where to.
The data is there, but scattered across tables and modules. Nobody has a complete picture per customer without first running an export and spending an afternoon in Excel.
Your customers, orders, invoices and history get a home in an open, in-house data layer. SAP doesn't have to go anywhere for this; the foundation lands alongside it, and you decide afterwards what still stays on SAP.
Orders, invoices, contact moments and documents per customer, together, live and searchable. No more exports and Excel.
Webshop, portal and integrations run on your own database. No more licensing question about who's allowed to touch your data.
SAP codes and table names are translated into an open model in your own language. Every developer, and every AI, can work with it.
Dashboards, AI chat and agents run directly on your own data layer. Reports that used to take days now appear in seconds.
Finance and logistics can just keep running in SAP. The data layer connects alongside it; full replacement can still happen later, whenever you want.
The data layer is open, portable PostgreSQL. You can always leave, even from us. That keeps everyone sharp, including ourselves.
2027 is coming, one way or another. The question is whether you'll be ready, or still stuck on the standard route.
Also read what the Data Act means for switching costs from 2027. On a different platform? There are also pages for Salesforce, HubSpot and Microsoft Dynamics 365.
No big bang and no multi-year project. The data layer lands alongside SAP, in five controlled steps, while everything keeps running as normal.
We map out which data lives where in SAP: customers, orders, invoices, custom code and integrations. You get an honest picture of what belongs in-house and where you genuinely still need SAP.
We retrieve the data via exports, RFCs and OData services. Coded SAP tables are translated into an open data model in your own language, with documentation included.
First a test migration. We recount per table, check relationships between customers, orders and invoices, and deduplicate. You review before anything becomes final.
SAP just keeps working while the data layer proves itself with a complete customer view, dashboards and AI on your own data. New data flows in automatically.
Keep SAP for finance and logistics with the data layer alongside it, or phase it out further over time: both are possible. The difference with today is that from now on, it's your choice.
You've heard big promises about migrations before.
That's why we start with a no-obligation data scan.
We look at your SAP environment together, map out which data needs to come out, and use a test export to show you what your data looks like in an open data layer. After that, you'll know exactly where you stand, even if you decide to stay where you are.
Yes. SAP data lives in well-documented tables and can be accessed via exports, RFCs, BAPIs and OData services. Customers, orders, invoices and history all come across completely. The real work is in the translation: SAP stores data normalised and coded, and during migration those codes get converted into a readable, open data model.
Usually not, and that's not the advice either. SAP is often the heart of finance and logistics, and it can stay that way. What does change: your customer and process data gets a home in an open, in-house data layer, which runs reporting, customer view and AI without SAP licences or consultancy. Full replacement can still happen later, whenever you want it.
SAP is winding down regular maintenance on the old ECC generation towards the end of 2027. Anyone still on it needs to move regardless. That's exactly the moment to look beyond the standard route to S/4HANA: which data and processes actually belong in-house, and where do you genuinely still need SAP?
Indirect access means that systems working with SAP data through an integration, such as a webshop or your own portal, can also be subject to licensing. You end up paying for your own software touching your own data. An open data layer alongside SAP reverses that: integrations and applications run on your database, with no licensing discussion.
The European Data Act requires cloud service providers to make switching possible, including handing over your data in a usable format. From 12 January 2027, no switching costs may be charged for this. Read more in our article on the Data Act.
Yes. The data layer runs on EU hosting with row level security, encryption at rest and in transit, and daily backups. The underlying infrastructure is SOC2 Type II and ISO 27001 certified. And because the environment is yours, you can verify that yourself instead of taking a vendor's word for it.
Everything about SAP's cost model, export routes and a migration with no data loss. Also valuable if SAP simply stays in place. Grounded, no sales pitch.
Leave your details and read the whitepaper online immediately, or save it as a PDF.
We only use your details to get in touch once about this service. No newsletter, no spam.
Enjoy the read. On the reading page you can also print the whitepaper or save it as a PDF.
Read the whitepaper