Moving to Odoo from the software you use today, without stopping the business.
Moving to Odoo from the business software you run today doesn't cost you a single working day of invoicing or orders. We clean and migrate products, customers, balances and open documents, reconcile them with your accountant, and switch over on a date we choose together.
MIGRATION CHECK
Example Company S.A. · trial migration 2 of 3
| Item | Your current software | Odoo | Check |
|---|---|---|---|
| Active products | 4,812 | 4,812 | match |
| Customers36 duplicates merged, with your approval | 1,342 | 1,306 | cleaned |
| Customer balances | €182,440.15 | €182,440.15 | match |
| Open invoices | 64 | 64 | match |
| Stock value€30.00 on one item · checked before the switch | €96,210.40 | €96,180.40 | difference |
The switch happens only when every row reads “match” or “cleaned”.
WHAT WORRIES YOU ABOUT THE SWITCH?
Whether it's a group bringing its Greek company onto Odoo or a local business leaving software it has used for years, the worries are usually the same four. All four are solved by preparation, not luck.
A closed sign on the door, because of a software change The business will stop
A day without invoices or orders costs money, and nobody wants to live it mid-week. So the final migration happens over a weekend, with files that have already been tested.
The final move happens over a weekend, with files that have already been tested.
A switch weekend, step by stepA customer's balance differs between the old and the new software The balances won't match
The fear is that a customer balance or the stock value changes on the way over, and the accountant finds out three months later. So we count every total before and after, and the switch happens only when they match.
We count every total before and after, and switch only when they agree.
What moves to Odoo and how we check itA customer list where the same customer appears twice Old mistakes will come along
Years in one system leave duplicate customers, products nobody sells any more and the same barcode on two items. We find them before the migration, and you decide what goes into Odoo.
We find them before the move, and you decide what goes into Odoo.
A colleague worries about the new software The team won't want to change
Whoever knows the old software by heart doesn't want to start from zero. They learn Odoo on your own data, weeks before the switch, so on Monday they already know what to click.
The team learns Odoo on your own data, weeks before the switch.
WHAT ODOO DATA MIGRATION INCLUDES
A written plan before anything moves
We list what your current software holds, who uses it for which job, and what each piece becomes in Odoo. You get the plan in writing, in English or Greek.
Data clean-up
Duplicate customers, wrong VAT numbers, inactive products, prices that make no sense: we show them to you in lists, and you decide what stays and what is merged.
Migration with checks
Every migration runs first on a copy of Odoo, two or three times, and we count records and totals before and after. It can run again without creating duplicates.
Parallel run
For a week or two your team also enters the day's transactions in the test Odoo, while invoices still come from your current software. Then we compare the results.
Training by role
Sales, warehouse and finance learn what each of them needs, on your own data, with written how-tos for the daily work, in English or Greek.
Greek suite and provider
Odoo starts with the Greek add-ons you need, and the connection to your e-invoicing provider moves to Odoo on switch day, with the same provider.
WHAT MOVES TO ODOO AND HOW WE CHECK IT
Not everything moves the same way. For each item we agree what is migrated, when, and which total it is checked against. The table usually looks like this:
Scroll sideways to see all columns
| Item | What goes into Odoo | When | How we check it |
|---|---|---|---|
| Products, codes, barcodes and price lists | Active products, after the clean-up | In the trial migrations, and again before the switch | Same number of active products, and sample prices from every price list |
| Customers and suppliers | No duplicates, with checked VAT numbers | In the trial migrations, and again before the switch | Each VAT number once; every merge approved by you |
| Open customer and supplier invoices | Each unpaid document, with the amount still due | On switch day | Their total equals the balances in your accountant's trial balance |
| Stock per warehouse | The counted quantities, with their cost | On switch day | Quantity times cost equals the inventory accounts |
| Open orders | Those not yet invoiced | On switch day | One by one, with the sales team |
| Opening trial balance | If the books will be kept in Odoo | Once your accountant closes the previous period | Balanced, and approved by your accountant |
| History of earlier years | Usually not; it stays in the old software | — | An archive you can search, for as long as you need it |
Your own table is written during the mapping.
A SWITCH WEEKEND, STEP BY STEP
This is how a company moves to Odoo, from Friday afternoon to Monday morning. Use the switch to see what happens when a balance doesn't match.
- Your current software
- The checks
- Odoo
- Your team
- Friday, 18:00. The last invoice is issued from your current software, and from then on nobody enters new transactions there.
- The final data comes out: customers, suppliers, open invoices, stock per warehouse and your accountant's trial balance.
- The checks compare every total with the trial balance: customer and supplier balances, open invoices, stock value.
- Everything matches, and the data goes into Odoo with the same files we tested twice in the previous weeks.
- One customer's balance comes out €120.00 higher than the trial balance. The migration stops there: nothing goes into Odoo half-done.
- We find the cause: a payment received on Friday was entered after the export. We show it to your accountant and export the file again.
- The checks run again, every total matches, and only then does the data go into Odoo.
- Saturday. Your accountant reviews the opening balances and the stock value in Odoo, and approves them.
- Monday, 08:00. Your team issues the first invoice from Odoo. It goes to the same provider as before, and the MARK number comes back onto the document.
- We stay close to the team for the first days. The old software stays open only so you can look things up.
WHEN TO SWITCH
We choose switch day with your accountant, so that each Greek VAT period comes out of one system only.
We avoid
- The last days of the month, when invoices close and the accountant prepares the VAT return.
- The middle of a VAT period, which would be split across two systems.
- The same week as a change of e-invoicing provider: one change at a time.
- Your peak weeks, such as holidays or sales, when nobody has time for training.
We choose
- The start of a VAT period, with the weekend before it for the final migration.
- A week when your accountant and your team are available.
- Only after two trial migrations have come out without differences.
- The start of the financial year, if preparation is done by November: for the books, it's the simplest switch.
Thinking of switching before 31 January 2027? Read first why it's safer to switch after the e-invoicing deadline, and see what changes in Greek e-invoicing.
YOUR PROVIDER STAYS THE SAME
If your Greek company already issues invoices through a licensed provider, you don't need to change it. When the connection runs through eInvoice Link, switch day changes only the system that sends the invoices: the old software until Friday, Odoo from Monday, to the same provider.
If your current software has its own connection to the provider, we check in advance that the same provider connects to Odoo too, and we test the connection in a test environment, not the live one.
From day one, Odoo also has the Greek add-ons you need: Greek charts of accounts, myDATA document types, delivery notes, payroll. How they are set up is in our guide Odoo and myDATA.
WHAT STAYS IN THE OLD SOFTWARE
Not every year of the company's history needs to move to Odoo. Active products, customers, open documents, stock and balances move; the history stays where it is.
You keep the old software read-only, for as many years as your accountant advises, to look up an old invoice or a customer's statement. If its licence is ending, we first export the history to files that open without it.
If you need some of the history inside Odoo, we move it separately: for example, past orders as opportunities in Odoo's CRM, so the sales team can see what each customer used to buy.
- The old softwareread-only
- Archivehistory in PDF and Excel
- Odoofrom switch day
MOVING TO ODOO WITHOUT LOSING ANYTHING
Changing your business software is scary because your data is your business. That's why every migration to Odoo is tested first and checked record by record.
- Wholesale and retail
From phone calls and spreadsheets to Odoo
Orders that arrive by phone and spreadsheet go into Odoo, with written procedures for checking and correcting them, and payments reconciled. Past orders become opportunities in the CRM, so you can sell to the same customers again.
Thousands of products, fully described
Technical attributes are filled in across the whole catalogue, and every record is read back from Odoo to confirm it went in correctly. Nobody has to eyeball thousands of lines.
- Eshop
Supplier price lists with no duplicate products
Supplier names, categories, prices and images load into Odoo. Every load runs first as a dry run that changes nothing, and however many times it runs again, it creates no duplicates.
- Eshop
We tidy up even the messiest files
Exports spread over several files, with active and inactive codes and variants, become checked import files with categories and attributes. Bring them as they are.
Thinking of moving to Odoo? Tell us where you're starting from and we'll tell you what it takes.
HOW MOVING TO ODOO WORKS, WEEK BY WEEK
As a guide, for a company with sales, inventory and invoicing:
Mapping
Weeks 1–2. We look at what your software holds and how you work, and write the plan: what moves, how it is checked, when the switch happens and at what price.
Clean-up and first migration
Weeks 3–4. We clean the data with you and run the first trial migration on a copy of Odoo.
Set-up and second migration
Weeks 5–6. We configure Odoo, the Greek add-ons and the provider connection in a test environment, and run the migration again with fresher data.
Parallel run
Week 7. Your team works in parallel in the test Odoo, and your accountant checks test documents.
Switch day
Week 8. The final migration happens over a weekend, and we stay close until the first month-end close.
QUESTIONS
What does moving to Odoo involve?
Moving to Odoo means taking a company off the business software it uses today and onto Odoo: its data is migrated after a clean-up, Odoo is configured around how it works, and the team starts working in Odoo from a set date. We split it into mapping, clean-up, trial migrations, a parallel run and switch day.
Will the business stop on switch day?
No. The final migration runs from Friday afternoon to Monday morning, with files we have already tested twice. On Monday your team issues invoices from Odoo. See it in the switch weekend.
Will all our history move to Odoo?
Usually not, and it doesn't need to. Active products, customers, open documents, stock and balances move. The history stays in the old software or in an archive, and anything you need inside Odoo we move separately.
What if a balance doesn't match?
The switch waits until we find the cause. Every total, from customer balances to stock value, is compared with your accountant's trial balance, and nothing goes into Odoo half-done. Try the switch «What if a balance doesn't match?» in the switch weekend.
Do we have to change e-invoicing provider?
No. You keep the same provider and subscription. If the connection runs through eInvoice Link, switch day changes only the system that sends it the invoices. If you don't have a provider yet, start there: see Greek e-invoicing.
Should we switch before 31 January 2027?
Usually not. Before the deadline it's safer to connect your current software to a provider, and move to Odoo afterwards, without the pressure. We explain why in the guide keep your ERP now, move to Odoo later.
Can our Greek company move into the group's Odoo?
Usually yes. We add the Greek company and the Greek add-ons to your existing database, migrate its data into it and test everything on a copy first. We work in English with your group's team and in Greek with your accountant. See Odoo for companies in Greece.
How long does it take, and what does it cost?
A move with sales, inventory and invoicing usually takes six to eight weeks. The cost depends on the volume and state of your data and on what we set up in Odoo; after the mapping we send a written proposal with a fixed price.
RELATED
Odoo Greece
Odoo set up for companies in Greece, with myDATA, delivery notes, ERGANI and payroll.
Greek suite for Odoo
Ten add-ons for what Greek law asks of a company, ready in Odoo from day one.
Greek e-invoicing
Your software connected to a licensed provider before 31 January 2027.
Guide: keep your ERP now, Odoo later
Why changing software is safer after the e-invoicing deadline.
Guide: Odoo first setup in Greece
Company details, VAT, numbering, warehouses, users and tests with your accountant.
Guide: what is an ERP
What business software does, what it's made of and when you need it.
TELL US WHAT YOU'RE MOVING FROM.
Tell us what your current software holds, and we'll send you a written migration plan with a fixed price.