odoobarcelona
← Back to the blog
GUIDE

Odoo implementation: the phases of a real project, one by one

Analysis, proposal and quote, configuration, data migration, training, go-live and support. What happens in each phase, what you have to do, which mistakes to avoid and what to prepare beforehand, for a Catalan SME.

Implementing Odoo is not installing a program. Installing it takes minutes; the hard part is making the software reflect how your company actually works: how you sell, how you buy, how you invoice, what your accountant needs and who should see what. An implementation is the road between the day you decide to change systems and the day your team works in Odoo without thinking about it.

After more than 900 implementations, what we have learned is that the phases are always the same, whether you are a twenty-person distributor or a five-person firm. What changes is how much each one weighs. In this article we walk through the seven phases, what we do and, above all, what you have to do, because the client's side is what most determines how the project ends.

An Odoo implementation succeeds or fails before anything is configured: it depends on whether decisions are made during analysis or left for go-live.

Before you start: what to have ready

You don't need anything to be perfect, but four things, if you have them, save weeks of conversations:

  • Someone in-house who makes decisions. They don't need to know about IT; they need to know the business and have the authority to say "this is how we do it".
  • The list of spreadsheets you use alongside your current software. Every spreadsheet is a process Odoo should absorb.
  • Your accountant's contact. If an external firm (a gestoría, in Spain) keeps your books, it must know from day one what it will receive and in what format.
  • An export of what you have now: customers, suppliers, products and, if any, open balances. If you come from Sage or A3, check whether you can export it yourself to Excel or CSV, because that changes the migration quote.

The phases, one by one

Analysis

This is the phase where we listen. We go through how you work today from end to end: how an order comes in, how it is prepared, invoiced and collected, how you purchase, and how all of that reaches the accounts. We also spot what lives on paper, what lives in spreadsheets and what only one specific person knows how to do. The analysis produces the list of apps you need and, just as important, the list of what you don't need yet.

What you do: explain how you really work, not how it should be. If a process has an exception that happens every week, this is the moment to say so. The typical mistake is presenting the ideal version of the business and discovering the exceptions on the first day of real work.

Proposal and quote

With the analysis done, we present a proposal: which Odoo edition suits you, which apps, how the data will be migrated and where it will be hosted. The quote comes from public rates: the base implementation goes from €4,500 with Community to €5,500 with Community Plus, €6,000 with Enterprise and €9,000 with Agentic, with five apps included and €350 for each additional app. Migration is €900 if you give us the data in Excel or CSV and €1,800 if we have to extract it ourselves from the old software. Community and Community Plus have no licence cost; Enterprise starts at €19.90 per user per month.

What you do: read the proposal looking for what is left out. The typical mistake is approving a vague scope and finding out later that an important part was missing. If you are torn between editions, the Community vs Enterprise comparison helps you decide before signing.

Configuration

This is where Odoo takes the shape of your company: tax details, chart of accounts, taxes, invoice sequences, VeriFactu, warehouses, price lists, users and permissions. We configure what was agreed during analysis and give you an environment where you can test before anything is final. Odoo can be used in Catalan, Spanish or English, and each user can choose their language; the documents your customers receive can also be issued in each customer's language.

What you do: test. Place an order, issue an invoice, record a purchase, as if it were a normal day. The typical mistake is asking for changes on every screen to replicate the old software. Odoo works best when you adapt to its standard flows and keep customisation for what truly sets you apart.

Data migration

We bring into Odoo what needs to stay alive: customers, suppliers, products, prices, opening stock and outstanding balances. If you come from Sage or A3, the usual approach is to migrate master data and open balances, and keep the history available in the old system or in an export, because migrating years of transactions usually costs more than it is worth. We decide this with you and your accountant.

What you do: clean up before migrating. Duplicate customers, products you no longer sell, records with a mistyped tax ID. The typical mistake is wanting to migrate everything "just in case" and starting in Odoo with the same clutter you had before.

Training

We train each person in what they will do, not in all of Odoo. Whoever invoices learns to invoice; whoever runs the warehouse learns to receive and prepare orders; whoever manages learns to read the reports. Training uses your migrated data, not generic examples, so the team recognises its own day-to-day work.

What you do: set aside time for the team. The typical mistake is squeezing training into whatever gaps the workload leaves and reaching go-live with people who have never touched the system.

Go-live

This is the day you leave the old system and start working in Odoo. You pick a date that makes sense: the start of a month or quarter makes life much easier for your accountant and for VAT closings. During the first days we stay close to answer questions on the spot.

What you do: close the old system to new transactions. The typical mistake is running both systems in parallel "for a few days" and ending up with invoices in both places and neither of them up to date.

Support

After go-live come the adjustments: a missing report, a permission that needs changing, a process that works differently day to day from how it was drawn. Support covers those adjustments, maintenance and upgrades. On Community Plus and Agentic we also maintain the Spanish localisation here: VeriFactu, SII and payroll.

What you do: note down what doesn't fit and report it early. The typical mistake is getting used to a small problem and working around it with a new spreadsheet on the side, which is exactly what the implementation set out to eliminate.

Your accountant, from day one

In Catalonia, most SMEs outsource their bookkeeping to a gestoría. That means the accounting firm is part of the implementation even if you are not paying it for that. It needs to validate the chart of accounts and taxes during configuration, agree with the migrated balances and know how it will receive information after go-live: direct access to Odoo or periodic exports. When the accountant learns about the change on the day of the first closing, the quarter gets complicated.

Mistakes that keep repeating

  • Wanting Odoo to be identical to the old software, screen by screen.
  • Rolling out every app at once when sales, purchasing and invoicing were enough to start.
  • Not having an internal person with time and authority to decide.
  • Migrating data without cleaning it.
  • Going live mid-month or mid-quarter without discussing it with the accountant.

None of these mistakes is technical. They are all about decisions, which is why they can be avoided if they are discussed during analysis.

Frequently asked questions

How long does an Odoo implementation take?

It depends on the apps, the volume of data to migrate and the time your company can dedicate to it. We won't give you a generic figure: the go-live date comes out of the analysis and is written into the proposal.

Can I migrate from Sage or A3?

Yes. If you give us the export in Excel or CSV, migration is €900; if we have to extract it ourselves from the old software, €1,800. The usual approach is to migrate master data and open balances.

Does Odoo work in Catalan?

Yes. Each user can work in Catalan, Spanish or English, and customer documents can be issued in each customer's language.

How much does it cost to implement Odoo?

The base goes from €4,500 with Community to €9,000 with Agentic, with five apps included and €350 for each additional app, plus migration if needed. You can work it out in the quote configurator.

Keep reading