- Home
- Services
Services
Services that cover an Odoo project from the first brick to after go-live.
At Codeator we implement, customize and support Odoo for holding companies and multi-entity businesses in Iraq, from studying the group’s companies and migrating their data to training their teams after go-live. Here is what each service includes, and what you receive.
What we offer
Seven services, one connected project.
Your group may need all seven in one implementation, or start with the one service it needs today. Either way, we agree the work and the deliverable first.
-
Odoo implementation
We configure Odoo on your group’s structure: companies, branches, currencies, a unified chart of accounts and inter-company rules, then test the cycles with key users before go-live.
You receive: a working system, separate books per company, consolidated group reports and a design document.
-
Customization and custom development
We start with standard Odoo, then develop what your business needs: invoice and report layouts in Arabic and English, approval cycles, and modules for progress billing or import costs.
You receive: documented developments, tested on a staging copy and written to Odoo’s standards so they survive upgrades.
-
Data migration
We move your data out of Excel, old accounting software and paper records: sources inventoried, duplicates removed, names and codes unified, accounts mapped, then a trial migration your team reviews.
You receive: opening balances that match your old records, clean master data and a reconciliation report your finance team signs off.
How we migrate data -
Training
We train every employee on their daily work by role and by company, on your own data: accountants, storekeepers, purchasing, sales and management.
You receive: teams that work on the system with confidence, key users in every company, and short Arabic user guides for each role.
-
Support and continuous improvement
We stay with your team after go-live: requests come through one documented channel, we work alongside finance through the first month-end close, and we review how the system is used.
You receive: a system that keeps pace as companies and apps are added, and a record of every request and its outcome.
-
Hosting and licensing advice
We compare hosting on your own servers with the cloud, size it from the number of companies, users and transactions, and identify the right Odoo edition; licences are quoted directly by Odoo.
You receive: a written hosting recommendation and specification, a test environment separate from the live one, and a backup plan.
-
Integration with other systems
We connect Odoo to the systems that keep running alongside it, from attendance devices and online stores to bank statements and specialist software, once we have defined which data moves, in which direction and when, through APIs or scheduled files.
You receive: a documented, tested integration, a log of what data moved and when, monitoring that records and resolves errors, and a clear procedure for when either side is down.
Data migration up close
From Excel, old software and paper to clean records in Odoo.
Data migration worries finance teams most when a system changes, so we treat it as a project of its own: each company’s data passes through a cleaning and mapping gate, and your team reviews it before a single line enters Odoo.
- Master data
- Customers, suppliers, products and the chart of accounts, unified across the group.
- Opening balances
- Account, customer, supplier and stock balances per company, in its own currency.
- Open documents
- Unpaid invoices, purchase and sales orders in progress, and live contracts.
- History
- We agree with your finance team what is migrated, and what stays in the old system.
- Trial migration
- A full migration into the test environment, reviewed by your team before go-live.
- Reconciliation report
- The old balances against Odoo’s after migration, signed off by your finance team.
How a project runs
Clear phases, and a deliverable at the end of each.
We build tier upon tier, and move to the next phase once the one before it has settled and your team has approved its outputs.
| Phase | What we do | What you receive |
|---|---|---|
| Consultation | We get to know the group’s companies and current systems, and what management expects. | A written outline of the implementation structure and its phases. |
| Discovery | Workshops with each company’s management and finance team on cycles, currencies, inter-company transactions and reports. | A requirements document, and a map of the group’s companies and their relationships. |
| Design | The company structure in Odoo, a unified chart of accounts, inter-company rules, access rights, and what needs development. | A design document your team approves, and a plan ordering the companies and apps. |
| Build | Configuring the apps and building the custom development on a staging copy, with regular demos for key users. | A staging system running on data from your companies, and a log of comments. |
| Migration and testing | Cleaning the data and running a trial migration, then an acceptance test in which key users run their full cycles. | A reconciliation report on the balances, and an acceptance record approved by your team. |
| Training and go-live | Training every role in every company, then the final migration and go-live, with our team following up. | A live system your team works on, and user guides in Arabic for each role. |
| Support and growth | Handling user requests, working alongside the first month-end close, then adding the next company or app. | A documented log of requests, and a plan for the next phase. |
In a holding company the design is done once for the whole group; the build, data migration and training phases are then repeated with each company that joins the system.
What the first consultation covers
A working session with your management or CFO, covering the map of companies, branches and currencies, the systems you work on today and the state of their data, the reports management is waiting for, and where to begin. It helps to have a list of the companies, samples of your monthly reports and a rough user count.
Book a consultationWorking with your group’s team
Two teams working as one.
An Odoo project in a holding company runs smoothly when the roles are clearly shared out from the first day. So before we start, we agree three things with you.
-
A steering contact on your side
One person from the group’s management, usually the CFO or operations director. They set priorities, settle where the companies differ, and approve each phase.
-
Key users in each company
One or two employees per company who know its daily work. They join the design workshops, test before go-live, then become the reference for their colleagues.
-
Documentation handed over to you
The design document, configuration guide, user guides and documentation of the custom development, kept by your group for your IT team and new employees.
On our side, one point of contact from the Codeator team works with you from discovery to go-live, with regular follow-up meetings, and every decision and change request stays documented and available to both sides.
Common questions
Questions we often hear about our services.
Can we start with a single service, such as training or data migration, outside a full implementation project?
Yes. Some companies ask for one service for an Odoo system they already run: training a new team, developing a report, migrating the data of a company that has just joined the group. We begin with a short review of the system, so the scope is defined precisely.
Can you take over an Odoo system another provider built?
Yes. We begin by reviewing the system’s configuration and the custom development added to it, and document what we find. We then agree the priorities with you: what needs attention now, and what can be improved gradually.
What data is migrated, and is the full history included?
We migrate the master data, opening balances and open documents of each company. For the history, we decide with your finance team what is migrated; the old system usually stays available for previous years.
Do we need an IT team inside the group?
A steering contact from management and key users in each company are enough to get the project under way. If you have an IT team, we work with it on hosting and backups, and hand over the full documentation.
Tell us about your group’s companies, and we will work out together where to begin.
In the first consultation we get to know your companies and their current systems, and propose the services you need and the order in which to deliver them.