Migrating to Odoo from Concar, Starsoft or SAP Business One is not copying the database. You migrate master data (chart of accounts, customers, suppliers and products), opening balances at a cut-over date and open documents; the history of previous years stays in the source system and in the electronic books already filed, or is loaded in summary. We do not use a direct connector between those systems and Odoo: data comes out as Excel, CSV or PLE TXT files, is transformed and imported with Odoo's templates.
At Ganemo we do it with an implementation methodology that already works, now powered by AI: your team decides what is migrated and validates each load, and your own AI agent prepares the files and loads them into Odoo. This guide explains what is migrated, how and with which risks.
How data comes out of each system
Before planning, it helps to know what your current system can export. This is what their own vendors publish:
| System | What it is | How data comes out |
|---|---|---|
| Concar (Real Systems) | Peruvian accounting software, in versions such as Concar SQL and Concar CB. | According to the official Concar SQL syllabus, it issues electronic books as PLE TXT files (sales, purchases, journal, ledger, cash and banks), SIRE files and reports in SUNAT format, and loads entries and sub-ledgers from Excel. |
| Starsoft | Peruvian ERP with accounting, payroll, electronic invoicing, purchasing, inventory and fixed assets. | Its website states that its accounting produces the PLE books; it does not publish a general exporter. In practice you work from its reports and the PLE TXT files. |
| SAP Business One | SAP's ERP for small and medium-sized companies. | SAP's help states that nearly all objects and data, including report results, can be exported to Excel. Its Data Transfer Workbench tool is for importing data into SAP, not for getting it out. |
Sources consulted on 20 November 2026. If your version exports differently, the method adapts; what does not change is that every file is reviewed before it is loaded.
What is migrated and what is not
| Data | Migrated? | How |
|---|---|---|
| Chart of accounts | Yes | It is compared with the PCGE that ships with Odoo's Peruvian localization, and your own sub-accounts are added or adjusted. It goes first, because everything else depends on it. |
| Customers and suppliers | Yes | With RUC or DNI, address and payment terms. Duplicates and invalid RUCs are cleaned up first. |
| Products and services | Yes | Categories first, then products, with unit of measure, cost and accounts. |
| Account balances | Yes | The trial balance at the cut-over date is loaded as the opening entry. |
| Open receivables and payables | Yes, only open ones | One record per document with its open balance, so they can be collected and paid in Odoo. |
| Opening inventory | Yes | Quantity and cost per product and warehouse. The total must match the inventory account in the trial balance. |
| Banks | Yes, the balance | The starting balance of the first statement in Odoo must be the real bank balance at the cut-over date. |
| Fixed assets | Yes | Acquisition value, accumulated depreciation and remaining useful life of each asset. |
| Entries from previous years | Usually not | They stay in the source system and in the electronic books already filed. If you need comparatives, summarised monthly balances are loaded. |
| Electronic documents already issued | Not re-issued | The XML files and receipts of documents already issued stay where they are; Odoo only receives the ones still open for collection or payment. |
| Payroll | Yes, if payroll moves too | Employee data and, if the switch happens mid-year, the year-to-date amounts that affect fifth-category tax, CTS and bonuses. More in payroll in Odoo. |
| Customisations and custom reports | No | They are not copied: we review which need they covered and solve it first with standard Odoo. |
How balances and history are loaded
The Odoo 19 documentation describes the order and precautions for loading the opening. Here is the summary, with the criteria we apply in Peru:
- Master data first. Chart of accounts, contacts, categories and products, using Odoo's import templates in Excel or CSV.
- Open invoices with their total balance. Each open invoice or bill is loaded with the amount due, not with its lines, so taxes are not recorded twice. Negative balances are loaded as credit notes.
- Opening balance with clearing accounts. In the opening entry, receivable and payable accounts are replaced by clearing accounts. That way the customer balance is not counted twice: once from the trial balance and again from the open invoices.
- Opening inventory. First each product's cost, then the counted quantities. The total value must equal the inventory account.
- Banks. The first statement starts from the real balance at the cut-over date; earlier transactions are not loaded.
- Final check. Clearing accounts must net to zero, and receivables, payables and inventory must match their details.
On history: the electronic books you already filed with SUNAT remain your record of earlier periods, and the source system is kept in read-only mode. Loading years of entries into Odoo makes the migration more expensive and is rarely used; if you need comparisons, monthly balances per account are enough.
How the cut-over works
The cut-over is the day the old system stops recording and Odoo starts. The simplest option is the start of a new fiscal year, because there is less data to move; if that is not possible, the cut-over is at the start of a month. Splitting a month is not advisable, because that period would have to be filed with data from two systems.
Cut-over steps
- Full rehearsal in an Odoo test database with real data, until the reconciliation comes out right.
- Close the last month in the old system: documents issued, electronic books or SIRE for the period and bank reconciliation.
- Decide on document series: continue the same ones from the next number or use new series. Never issue from both systems at the same time.
- Load balances, open items, inventory and banks into production, following the rehearsal procedure.
- Your accountant reviews the reconciliation and Odoo issues its first document.
The books and registers for the first month in Odoo already come from Odoo. What standard Odoo covers and what our modules cover is detailed in Peruvian Odoo localization.
Migration risks and how to avoid them
- Duplicated balances. Loading the trial balance with receivables plus the open invoices doubles customer debt. Clearing accounts prevent it.
- Badly mapped chart of accounts. A wrong account goes unnoticed until the first electronic book. Reviewing the mapping with your accountant before loading anything prevents it.
- Inventory that does not reconcile. If the loaded inventory value does not match the books, cost of sales is wrong from day one. A physical count and reconciliation before the cut-over prevent it.
- Dirty master data. Duplicate RUCs, repeated products or incomplete addresses carry over as they are. They are cleaned at the source or in the load file.
- Wanting to migrate everything. Bringing years of history and every customisation of the old system lengthens the project and reproduces old problems. What is and is not migrated is agreed in writing.
- Cutting over in the middle of a tax period. It forces you to combine two systems for a single return. Cutting over at the start of a month or year prevents it.
How we do it at Ganemo
Method first. Your team learns Odoo and leads the migration: it decides which data moves, reviews the reconciliations and approves each load. Training is at the centre, agreements are written down (what is migrated, what is not and the cut-over date) and we start with standard Odoo before thinking about development.
Then, AI as an accelerator. Your own AI agent (Claude Code or ChatGPT Codex) connects to Odoo with keys stored in Secrevo. The agent turns the Concar, Starsoft or SAP Business One exports into import files, checks RUCs, accounts and reconciliations, and loads them first into the test database and then into production. Your accountant reviews each result before moving on. How to connect the agent securely is explained in how to connect Odoo to Claude Code or ChatGPT Codex.
We do not sell certificates, we deliver results. If you come from SAP Business One and are still comparing, see Odoo vs SAP Business One; if you have already decided, see what an Odoo implementation in Peru looks like.
Frequently asked questions about migrating to Odoo
We do not use one. Data is exported from the source system as Excel, CSV or PLE TXT files, transformed and imported with Odoo's templates. That way every file is reviewed before it is loaded.
It can be, but it rarely pays off. The usual approach is to migrate opening balances and open items, and keep the history in the old system and in the electronic books already filed. If you need comparatives, monthly balances per account are loaded.
The start of a fiscal year, because there is less data to move. If that is not possible, the start of a month. Avoid splitting a month so you do not file one period with data from two systems.
It depends on data volume, how clean the data is and how many apps go live at once. That is why it is planned with a full rehearsal in a test database; the rehearsal shows how much real work there is before the cut-over.
No. Documents already issued are not re-issued and their files stay where they are. Odoo receives the ones still open for collection or payment, to manage them from there.
Coming from Concar, Starsoft or SAP Business One?
We review with you which data you have, how it comes out and which cut-over date suits you. Write to us or call +1 (828) 672 6150. We serve companies worldwide and are present in Peru, Paraguay, Chile, Mexico, the US, Ecuador, Colombia, Argentina, Spain, Nicaragua and the Dominican Republic. Is your country not on the list? Your company can be the first.