Our Odoo services: from audit to support, a single point of contact.
Scoping, migration, sovereign hosting, support & maintenance, training, funding: everything around your ERP, operated by the team that deployed it — 350+ projects since 2013.
An ERP is not just installed software: it has to be scoped, migrated, hosted, evolved — and the people who use it trained. As anOdoo integrator in Morocco and publisher of the Karizma One platform, we cover the whole cycle — with firm scoping at the start, a contractual Go-Live and continuous support afterwards. Each service below has its own detailed page.
Nine services, one standard of excellence
Our deployment method
Firm scoping, design, build, deployment and run: the five phases, their deliverables and exit criteria.
Discover →AI & Digital 360 audit
Diagnosis of your processes, your existing system and your digital maturity, with a prioritised roadmap.
Discover →Odoo migration
From Sage, SAP, Excel or an older Odoo version: data migration, secured cut-over, training.
Discover →Sovereign hosting in Morocco
Your data stays in Morocco, on a monitored, backed-up and compliant infrastructure.
Discover →Support & maintenance
Corrective and evolutionary maintenance, contractual SLAs, and unlimited bug fixing for Karizma One clients.
Discover →Odoo training
Users, administrators, key users: learning paths adapted to each role, on your own configuration.
Discover →Pricing & budget
Price grid, packages and cost calculator to build a realistic budget before you commit.
Discover →Implementation timeline
From 6 to 25 weeks depending on scope: what drives the duration, and how to secure it.
Discover →Grants & funding
Up to 70-90% of the project funded: eligible programmes and application support from our teams.
Discover →A controlled framework, from the first workshop to continuous support
Scope, schedule and budget fixed at scoping. A contractual Go-Live. Support that does not stop at go-live. That is the difference between a delivered project and a successful one.
See the five phases →What each engagement includes
For each service: who it is for, what is delivered, how long it takes, and the point on which we do not compromise.
Scoping and audit
Who it is for. Executive management or IT directors who must choose between several scenarios before committing a budget.
What you receive. A map of your existing processes, a gap matrix against standard Odoo, a costed scope by batch, a macro schedule and a budget estimate within ±15%.
Typical duration. 2 to 4 weeks depending on the number of business areas involved.
Our sticking point. A rushed scoping is paid for in change orders. We refuse to price a project whose critical processes have not been observed in the field.
Integration and deployment
Who it is for. Companies of 20 to 500 employees replacing an ageing ERP or moving off Excel.
What you receive. Full configuration, custom developments, migration of historical data, assisted business acceptance testing, key-user training and go-live support.
Typical duration. 3 to 9 months depending on the number of modules and sites.
Our sticking point. Data migration is systematically underestimated. We treat it as a work package in its own right, with its own validation milestones.
Odoo migration
Who it is for. Companies already on Odoo, stuck on an old version or on unmaintainable custom code.
What you receive. An audit of the existing code, rework or removal of obsolete developments, data migration, regression testing, and the switch to production.
Typical duration. 6 to 14 weeks depending on the volume of custom code.
Our sticking point. Migrating without pruning simply carries the debt over. We always start by identifying what can be removed.
Hosting and managed services
Who it is for. Organisations subject to sovereignty or contractual availability requirements.
What you receive. Hosting in Morocco on the Karizma One platform, tested daily backups, monitoring, separate test and production environments, and update management.
Typical duration. Live within 5 working days.
Our sticking point. A backup that has never been restored is not a backup. Our restores are tested at regular intervals.
Support and maintenance
Who it is for. Teams in production who need a named contact rather than an anonymous helpdesk.
What you receive. Functional and technical support with response-time commitments, fixes, small enhancements, version monitoring and a periodic review meeting.
Typical duration. Annual commitment, with an hours volume that can be adjusted during the contract.
Our sticking point. Support that only fixes lets the system stagnate. We reserve part of the package for enhancements.
Formation
Who it is for. End users, key users and administrators who need to become self-sufficient.
What you receive. Role-based learning paths, built on your own instance and your own data, with materials provided and an end-of-course assessment.
Typical duration. 1 to 5 days depending on the path, on site or remotely.
Our sticking point. Training on a demo database achieves nothing. Our sessions run on your real configuration.
Who does what, at each phase
The most common cause of drift is not technical: it is unclear responsibilities. Here is the split we put in the contract.
| Phase | Content | Karizma | You |
|---|---|---|---|
| Scoping | Field observation, business interviews, gap matrix. | We produce the scope and the pricing. | You appoint a lead per business area and approve the trade-offs. |
| Design | Target configuration, development specifications, migration plan. | We write the specifications and build prototypes. | You approve every mock-up before development. |
| Build | Configuration, developments, integrations, test data sets. | We build and unit-test. | You provide the reference data and the business test cases. |
| Acceptance testing | End-to-end business testing, correction of gaps, key-user training. | We fix and train. | You run the acceptance tests and sign off. |
| Go-Live and stabilisation | Switchover, enhanced assistance, handover to support. | We are on site during the first days. | You mobilise your teams over the critical period. |
This split is carried over unchanged into our commercial proposals. It is detailed in our deployment method and put into practice from the scoping workshop.
Three engagement models
The right model depends on how mature your need is, not on the size of the project.
Fixed price
Fixed scope, firm price, payment milestones tied to deliverables.
When to choose it. Appropriate when scoping has been done properly and the need is stable.
Its limit. Any deviation goes through a change order: that is the price of predictability.
Managed time and materials
A dedicated team, a contracted volume of days, sprint-based delivery.
When to choose it. Appropriate for exploratory projects or scopes that evolve along the way.
Its limit. It requires real availability on the client side: without quick decisions, time and materials drifts.
Fixed-price maintenance
An annual envelope of hours, response-time commitments, a review committee.
When to choose it. Appropriate once in production, to smooth the workload and keep the system alive.
Its limit. The volume is recalibrated at year-end based on actual consumption.
Budget ranges by company size are detailed on the Odoo pricing in Morocco page, and funding schemes on digitalisation grants.