SAP implementation
SAP Business One and S/4HANA, implemented with Romanian localisation and a migration plan that does not stop production.
What it actually is
SAP earns its place in two situations: the company has outgrown what a mid-market ERP can cover, or the group you belong to mandates the platform and its reporting format. Otherwise other platforms cost considerably less for the same result, and we say so before anything is signed.
We work on SAP Business One for mid-sized companies and on S/4HANA for large ones or for subsidiaries integrated into a group system. We implement, we migrate from legacy systems, and we take over support of systems installed by somebody else.
A SAP project is almost always lost on master data and undecided processes, not on technology. That is why the first weeks go on cleaning master data and making process decisions, before any configuration.
Who it is for
- Companies above roughly 100–150 users with complex manufacturing or distribution processes.
- Romanian subsidiaries of international groups reporting consolidated in SAP.
- Industries with strict batch and serial traceability requirements.
- Companies already on SAP but on an old version, preparing the move to S/4HANA.
- Organisations with a SAP installed by someone else, looking for a local support partner.
Who it is not for
- Companies under 50 users with standard processes. The total cost of ownership does not justify itself, and alternatives do the same job.
- Projects looking for the lowest implementation price. Cheaply implemented SAP costs more than expensively implemented SAP.
- Organisations without the internal capacity to keep master data clean after go-live.
What we actually do
Fit-gap analysis against the standard
We compare your processes with standard SAP processes and decide, point by point, what adapts to the standard and what genuinely needs development. Every deviation carries a cost for the life of the system, and we write it down.
Configuration and Romanian localisation
Chart of accounts, journals, VAT, e-Factura to SPV, e-Transport, statutory declarations and the data structure for SAF-T (D406).
Master data cleaning and migration
Materials, partners, price lists, balances, stock, open orders. We run repeated rehearsal migrations with a balance reconciliation after each one.
Developments and interfaces
Reports, forms, extensions and interfaces to other systems, built within platform-supported limits so future upgrades stay possible.
Integration and acceptance testing
Scenarios that cross the whole order-to-cash flow, run by your users on their own data, against acceptance criteria written in advance.
Go-live and hypercare
A planned cutover with people on site and a team available through the first weeks, up to the first month-end close.
Ongoing local support
We also take over systems implemented by other partners. We start with an audit of the existing configuration and developments, so we know what we are taking on.
How long it takes
- 1
Fit-gap analysis and design
6–10 weeksProcesses, deviations from standard, acceptance criteria and migration plan.
- 2
Configuration and development
10–20 weeksBuilding the system, with periodic demos on complete processes.
- 3
Migration and integration testing
6–10 weeksRehearsal migrations, reconciliations and acceptance testing.
- 4
Training and go-live
3–5 weeksRole-based training, planned cutover and on-site assistance.
- 5
Hypercare and stabilisation
6–10 weeksFixes, adjustments and the first month-end close in the new system.
What you supply
- An internal project manager, full-time for the duration.
- Named process owners for each functional area.
- The master data, with your team owning the cleaning of it.
- Group reporting requirements, if any, in writing.
- An available test environment and users freed for acceptance testing.
What it costs
SAP projects are contracted by stage, at a fixed price per stage once the fit-gap analysis is complete. The analysis is contracted separately, precisely so the estimate that follows it is real.
Fit-gap analysis and implementation estimate
per project
6–8 weeks
Includes
- Documentation of current and target processes
- List of deviations from standard, with lifetime cost
- Data migration plan
- Implementation estimate with fixed price per stage
SAP Business One, full implementation
per project
6–9 months
Includes
- Configuration and Romanian localisation
- Master data and balance migration
- Reports, forms and up to three interfaces
- Training, go-live and hypercare
S/4HANA or group projects
per project
9–18 months
Includes
- Scope fixed after the fit-gap analysis
- Alignment to the group process model
- Legacy migration with reconciliations
- Integration testing and formal acceptance
Local SAP support, monthly
per user / month
Includes
- Guaranteed incident response time
- A monthly budget of hours for adjustments and reports
- Fiscal localisation updates
Indicative prices for our services, excluding VAT. SAP licences and infrastructure are contracted separately, direct with SAP or with the hosting provider.
Configure an estimateFrequently asked questions
What does a SAP implementation cost in Romania?+
SAP Business One starts at €65,000 for implementation services, and S/4HANA or group projects at €140,000. We recommend contracting the fit-gap analysis separately, from €9,500, because only after it does the estimate become real. SAP licences are contracted directly with the vendor.
SAP Business One or S/4HANA?+
Business One covers mid-sized companies with ordinary distribution or manufacturing processes. S/4HANA earns its place at high volumes, in structures with several legal entities, or where the group mandates the platform and its process model. The fit-gap analysis answers this with arguments and costs rather than preferences.
Will you take over support of a SAP someone else implemented?+
Yes, it is a significant part of what we do. We start with an audit of the existing configuration, developments and interfaces, so we know exactly what we are taking on and what risk it carries. Contractual response times are set only after that audit.
Does SAP cover Romanian fiscal requirements?+
Yes, with the localisation configured properly: Romanian chart of accounts, VAT journals, e-Factura to SPV, e-Transport and the data structure for SAF-T (D406). Localisation does not arrive working out of the box — it is implementation work, and we put it explicitly in scope.
How long does a SAP project take?+
Six to nine months for a Business One implementation of ordinary complexity, and nine to eighteen months for S/4HANA or group projects. Those timelines include data migration, acceptance testing and the hypercare period after go-live.
Related services
ERP implementation & support
From choosing the system to the first month closed inside it — and afterwards, for as long as you need us.
Odoo ERP implementation
We implement Odoo module by module, in the order that pays you back — not the whole system at once in a one-year project.
IT architecture design
We draw the system before it is built — which components exist, how they talk, what happens when one fails, and what the whole thing costs.
Shall we talk about your project?
Thirty minutes, no obligation, at the end of which you know whether we can help and roughly what budget it takes.