Start with the database
If you’re planning a migration — or suspect you need one — send me a few lines about what you’re running. Rough is fine; I’ll ask the follow-up questions.
What to include
- Your current version (13, 14, 15, 16?) and, if you know, where you’d like to end up
- Rough size — users, database size, how many companies or websites
- Custom modules — how many, who built them, whether the source is available
- Integrations — what Odoo talks to: shop, accounting, carriers, in-house systems
- What worries you — downtime, data loss, a past migration that went badly
I read every message myself and reply to project enquiries within 24 hours.
Elsewhere
- Upwork: https://upwork.com/freelancers/~01b4a3b4a4b4a4b4
- LinkedIn: https://linkedin.com/in/babatopeajepe
- GitHub: https://github.com/babatopeajepe
How it usually goes
A first call
We talk through what you’re running, what’s in the way and what a good outcome looks like. This is where I figure out whether I’m the right fit.
An assessment
For migration work, this is the real starting point: I audit the custom modules, database size, integrations and risks, and you get a written plan with a fixed quote.
Staging, then cutover
The upgrade happens on a staging copy first, with you testing as long as you need. The cutover itself is rehearsed, scheduled around your business, and reversible.
Questions people often ask
How soon can you start?
It depends on what I’m working on, but usually within 2 to 4 weeks.
Do you work with clients in other time zones?
Yes. I work with clients all over the world. We find meeting times that suit both of us and handle the rest in writing.
How do you structure a project?
For migrations: assessment, staging upgrade, verification, then a rehearsed cutover. For everything else, short iterations with a demo at the end of each one. On small jobs that can all happen in a week.
Can I talk to past clients?
Yes. After our first conversation I can share references and examples from similar projects — including the 14 → 16 migration behind the case study.
What happens after the migration?
I offer ongoing support for bug fixes, checks and small improvements. Migrations also tend to surface performance work, which I’m happy to quote for separately.
Other work
Not everything is a migration. I also take on:
- Custom development — modules and automations the standard apps don’t cover
- Integrations — connecting Odoo to your shop, carriers, accounting tools or in-house systems
- Performance — finding out why things are slow (queries, config, code, crons) and fixing it
- Consulting and support — code reviews, architecture advice, and ongoing help once a project is live
Got a migration in mind?
Send me a few lines about what you're running. Rough is fine — the assessment turns it into a plan.