- Home
- Our services
- SAP · S/4HANA & ERP
SAP services
Which transformation scenario is defensible in your context?
Conversion, new implementation or selective transition. Private cloud, public cloud or local hosting. The right scenario is the one that can be demonstrated on your custom-code debt, your processes, your data, your calendar and your budget. We examine it with you, then we deliver it, from framing to go-live. And when SAP S/4HANA is not the right answer, we say so: SAP Business One or Odoo serve many SMEs better.
The decision at stake
2027 is not the issue.
The decision is.
Mainstream maintenance for SAP Business Suite 7 ends at the end of 2027. Extended maintenance, optional and paid, runs until the end of 2030. The question is therefore not "when should we migrate", but what decision to take now to stay in control of the calendar, the budget and the scenario.
Migrating "as is" to meet the deadline means paying the price of a program without reaping its benefits. Rebuilding everything indiscriminately makes timelines and risks explode. In between, a decision grounded in facts: your existing system, your business priorities, your capacity to absorb change. What West African companies need to decide →
The decision matrix
The right scenario is the one that can be demonstrated.
Seven criteria, three scenarios. We examine them in an audit of your existing system, like an investment decision: full costs, risks, benefits, pace. The reading below is indicative. Your own file decides.
| Criterion | Conversion brownfield | New implementation greenfield | Selective transition selective data transition |
|---|---|---|---|
| Custom-code debt | Low to moderate, cleaned up before cutover | High: the legacy is no longer worth carrying | High on certain scopes only |
| Process quality | Sound processes, to be kept | Processes to be rethought to the standard | Mixed: keep here, rebuild there |
| Standardisation ambition | Continuity first | Standard from day one | Targeted standardisation by flow |
| Data | History kept, cleaned | Selective takeover, master data redesigned | Takeover à la carte, by company or by flow |
| Duration | The shortest | The longest | Intermediate, in waves |
| Risk | Technical, controlled through rehearsals | Business and change management | Governance and consistency across waves |
| Budget | The most contained | The highest, for the broadest value | Adjustable, scope by scope |
The targets
Private cloud, public cloud, local hosting: a target is chosen.
The transformation scenario and the hosting target are two linked decisions. From Dakar, they are also read in latency, data residency and foreign-currency cost. We examine them together, on the building blocks we actually implement. SAP in private or public cloud from Dakar: what to look at →
- RISE with SAP
The modernisation path for an existing ERP towards a private cloud, in a single contract bringing together platform, infrastructure and updates. Relevant when the existing system is rich and the need for continuity is strong. We assess the opportunity, then we run the migration.
- GROW with SAP
SAP S/4HANA Cloud, public edition, continuously updated by the vendor. The scenario for organisations that accept the standard to gain deployment speed and lower operating cost. Often the right entry point for a growing company or a new subsidiary.
- SAP Business One
The SAP ERP for SMEs and modest-sized subsidiaries: finance, sales, purchasing, inventory in a single system, with SYSCOHADA financial statements. A proportionate answer when SAP S/4HANA would be oversized.
- Odoo
For SMEs outside the scope of SAP, we implement Odoo, of which we are a partner. The same demanding method: clarified processes, data taken over cleanly, teams trained before go-live.
- Clean core
Extensions move out of the core. A system that keeps up with updates and adopts the vendor's innovations without regression. An economic discipline before it is a technical one. What really needs governing →
- SAP BTP
The platform for extensions, integrations and AI use cases around the core. This is where what the standard does not cover gets built, without compromising the clean core.
The regional context
An ERP that speaks SYSCOHADA.
An ERP in Senegal or across UEMOA must produce the financial statements of the revised SYSCOHADA (balance sheet, income statement, cash flow statement, notes), handle Senegalese VAT and the national tax rules of each country in the group, in a single currency, the CFA franc. Regional groups are multi-company and multi-country. Goods flow through the Port of Dakar and its traceability requirements. We configure SAP within this framework, with finance leadership. Our Finance expertise →
Our approach
A prepared cutover beats a rushed cutover.
SAP Activate is our reference framework. We adapt it to the chosen scenario and to your governance. What does not change: Design Authority, fit-to-standard, gap management, data preparation, rehearsed cutover and hypercare. Our approach in detail →
Assess
Analysis of the existing system: processes, custom developments, data quality, technical debt. A factual assessment, the basis for everything else.
Decide
Informed comparison of the scenarios and the hosting target, a choice arbitrated by your management on explicit criteria.
Prepare
Data cleansing, reduction of custom code, focus on the standard core, cutover and fallback plan. The success of go-live is decided here.
Cut over
Conversion or implementation in waves, demanding test cycles, cutover rehearsals, coordination of the vendor and, where applicable, a third-party integrator, up to a go-live with no surprises.
Realise value
Stabilisation, adoption, then activation of what SAP S/4HANA makes possible: faster closings, embedded analytics, unified master data, AI at the heart of processes.
Our typical deliverables
What you hold in your hands, at every step.
Business case
Full costs over several years, in CFA francs and in foreign currency, expected benefits, compared scenarios. The document on which your management decides.
Readiness assessment
Processes, custom code, data, integrations: the readiness of your existing system, item by item, with the prerequisites to clear.
Target architecture
Core, SAP BTP extensions, integrations, data, security, hosting. The target drawn before buying, governed during the project.
Simplification backlog
The prioritised list of custom developments to remove, replace with the standard or move out of the core, with the cost of each option.
Conversion setup
A conversion and testing setup that can be replayed at every cycle, making the calendar predictable.
Cutover plan & hypercare
The minute-by-minute cutover plan, its entry, exit and rollback criteria, then the first weeks of operation at your side.
What we take on
From scenario choice to go-live.
On these projects, AGILICIS acts as integrator: the conversion or implementation is carried out by our own teams, from SMEs to large regional groups. When another integrator holds the build, we move to your side of the table, as client-side project support. Ways of working with us →
- Scenario study
Audit of the existing system, informed decision matrix, RISE with SAP, GROW with SAP or local hosting opportunity, full costs and a realistic calendar.
- Standard core
Inventory of custom developments, documented standard-versus-custom decisions, extensions moved to SAP BTP. A system that stays upgradable.
- Process design
Fit-to-standard, flow simplification, gaps documented and governed by the Design Authority, built with the business teams.
- Data & migration
Cleansing, master data, selective or full takeover strategy, controls and reconciliations at every cycle.
- Cutover & testing
Test strategy, dress rehearsals, cutover and rollback plan, go-live command centre.
- Adoption & run
Training, support of key users, hypercare, then handover to support and continuous improvement. Support & application management →
The entry offer
The 2027 Framing.
Before committing to a program, settle the decision. The 2027 Framing takes a few weeks, not months. It ends with three deliverables on which your management can decide.
- A quantified assessment
Processes, custom developments, data quality, technical debt: what your existing system weighs, established item by item.
- A recommended scenario
Conversion, new implementation or selective transition, private, public or local target: the recommendation argued on the matrix, with its explicit conditions for success.
- A roadmap
Milestones, prerequisites and sequencing up to go-live, aligned with your real capacity to absorb change and with the 2027-2030 deadline.
The technology
The building blocks we put to work.
An SAP S/4HANA transformation is judged six months after go-live: simpler processes, faster decisions.
Your decision
Which scenario is defensible for you?
A first conversation with a senior consultant to situate your existing system and objectify the scenarios, before the calendar decides for you.
Let's talk →