MK Moad Khider
FREN
Write

Odoo consultant · remote · Boulogne-Billancourt

Your Odoo
changes version.
The person you call does not.

Launch it, fix it, migrate it, or keep it running. Six years, from version 11 to 19, Community and Enterprise.

Describe what I needCall

Quote within 48 hours.

$ status --deploy
v11  start
v14  team
v16  Paris
v19  now
  • v16
  • v17
  • v18
  • v19
  • v20

Already handled on real projects

The apps the work actually touched.

Integrations already shipped: Stripe, Salesforce, ServiceNow, WhatsApp, GitHub, Google Storage, SFTP, Power BI.

Four ways in

The need decides where we start. Often they end up holding each other.

01

Launch my Odoo

  • Hosting, domain, email
  • French localization, access, users
  • Data import and a first training

02

Improve or fix

  • Audit and bug fixes
  • Modules, views, automations, Studio
  • Integrations and performance

03

Migrate

  • A version upgrade, or another tool
  • Data cleaned up
  • A parallel run, then the switch

04

Keep it running

  • Backups and monitoring
  • Training and reserved hours
  • So production stays in place

Also, when a local business needs it: a light site, online ordering, appointments.

Markers

6years on Odoo
11→19versions carried
100+people trained
v15certified consultant

What the work changes

Three situations that kept coming back.

Integration

Odoo and Salesforce stop doubling each other.

Before. The same accounts live in two tools. Someone retypes them, and the two drift apart.

Done. A bridge that exchanges and syncs data between the two systems.

Migration

The next version takes the custom work with it.

Before. An Odoo that grew up. Modules that are afraid of the upgrade.

Done. Data carried over, modules adapted, tests, then the switch. From 11 to 13, and later on up to 19.

Production

The server is part of the delivery.

Before. The app is ready. Nobody knows who sets the domain, the certificate, the backups.

Done. Linux, Nginx, DNS, HTTPS. The job ends when it is online.

How a project moves

  1. 01

    Scoping

    Workshops, the need, written specifications. We know what is in scope before the first line.

  2. 02

    Building

    Modules, reports, integrations, or a migration. Each project moves with its own acceptance.

  3. 03

    Handover

    Documentation, training, go-live. The next person can take over without a call for every screen.

The path

  1. 2020Casablanca. Gold integrator. Migration 11 to 13, then a team.
  2. 2022Nantes. Silver integrator. Pre-sales, MRP, Salesforce bridge, upgrades to 15 and 16.
  3. 2023Paris. Inventory and logistics, then sales, purchase, events, ServiceNow.
  4. 2025Independent. From 16 to 19, remote. Certified Consultant v15.

Questions that come up fast

Do you travel to the client?

No. Projects are remote. Workshops happen on video. Boulogne-Billancourt is the time zone, not a waiting room.

Which versions, Community or Enterprise?

From 11 to 19, depending on the project. Community and Enterprise. Odoo.sh, a server I set up, or Odoo Online.

Does a migration break custom code?

That is the work. Carry the data, adapt the modules, test, and only then switch.

Do you train the teams?

Yes. More than a hundred people have been trained, with documentation that stays after the project.

How do I get a quote?

Write the version and what is stuck. The quote goes out within 48 hours.

What about French e-invoicing?

It can be part of a project. I do not give legal advice, and I do not promise compliance.

Describe what I need