SAGE PASTEL TO ODOO MIGRATION | SERPA ODOO ERP FOR AFRICA

A finance team can close a month in Pastel and still be unable to answer a basic operational question the next morning: which branch has the stock, which customer account is overdue, and whether the invoice issued yesterday meets the local tax rule. That gap becomes urgent when a business adds entities, warehouses or regulated e-invoicing requirements.

A Sage Pastel to Odoo project is not a file conversion. It is a new ERP implementation, with a controlled data migration, localised tax configuration and a cutover plan that must stand up to finance, operations and audit review. For organisations planning a migration to Odoo (from Pastel, QuickBooks, Sage, SAP), the decision is less about whether a CSV can be uploaded and more about which records, controls and operating rules should exist on day one.

We see one mistake more than any other: treating historical data as the project. It is not. A clean opening position, open customer and supplier items, usable stock records and tested compliance are usually more valuable than importing every transaction from the last five years.

What a Sage Pastel to Odoo migration actually involves

Odoo’s upgrade service does not cover a move from another ERP. That matters because a Sage Pastel to Odoo migration requires its own scope, team, testing and sign-off process. Data must be extracted from Pastel, mapped to the Odoo structure, cleansed, loaded, reconciled and approved before users operate in production.

As of October 2026, Odoo 19 documentation is the current implementation reference. It supports CSV and XLSX imports for common records, but an import is permanent. A test import is therefore not optional. It is the point at which duplicate contacts, invalid account mappings and bad dates become visible while they are still inexpensive to correct.

We recommend external IDs for imported records. They allow the implementation team to rerun a corrected import without creating a second copy of every supplier, product or customer. Without external IDs, a reloaded contact list can leave finance staff choosing between near-identical account records during collections or payment allocation.

What normally transfers

The following data types can normally be transferred through Odoo CSV or XLSX imports, subject to data quality and a defined mapping specification:

| Pastel data area | Can it transfer? | What must be checked before loading | Why it matters | | Customers and suppliers | Yes | Legal names, tax identifiers, addresses, payment terms and duplicates | Incorrect master data creates invoice, collection and supplier-payment errors from the first day. | | Products and services | Yes | Product codes, units of measure, taxes, costing fields and categories | Product records affect sales pricing, purchasing, stock and accounting postings. | | Bank statements | Yes | Dates, references, opening position and reconciliation status | A bank import cannot compensate for an unreconciled Pastel cashbook. | | Journal entries | Yes | Account mapping, dates, references and audit support | Finance needs a traceable opening position and a defensible audit trail. | | Sales and purchase orders | Yes | Customer or supplier match, products, prices and order status | Open commitments must remain visible to sales, procurement and operations. | | Open invoices and bills | Yes | Outstanding amounts, due dates, tax treatment and allocations | These records drive debtor follow-up, creditor payments and cash forecasting. | | Inventory opening balances | Yes | Product, quantity, location, lot or serial number and valuation | Stock quantities without matching value will break the opening financial position. |   The data sequence is just as important as the data itself. We configure the chart of accounts first, then taxes, journals, products and contacts. After that come open invoices and bills, opening stock, the opening trial balance and finally opening bank balances.

That order follows Odoo’s accounting implementation guidance. Dependent records need the chart of accounts and tax structure already in place. If a team loads invoices before agreeing the receivables accounts, tax mapping and journals, it creates rework rather than progress.

Keep useful Pastel codes, but do not damage Odoo defaults

Many CFOs want to retain familiar Pastel account codes because management packs, audit files and finance team habits are built around them. That can be sensible. We can retain or recode equivalent accounts where the finance design supports it.

The line we do not cross is changing or deleting the type of Odoo standard accounts used as defaults. Odoo relies on those account types for its accounting behaviour. Rename or recode an equivalent account where needed, then create additional accounts only where there is a genuine reporting or statutory requirement.

This is a judgement call, not a purity test. If a group has one established reporting code structure across several entities, preserve it where practical. If the existing Pastel chart has duplicate expense accounts, inactive control accounts and codes nobody can explain, do not reproduce the clutter in Odoo.

What does not transfer automatically

Data can move. Operating design does not move by itself.

Pastel-specific custom reports, user permissions, approval rules, integrations, document layouts, tax mappings, stock costing choices and bespoke workflows require redesign or configuration in Odoo. They must then be tested with the people who will approve payments, issue invoices, receive stock and close the month.

| Item in the Pastel environment | Automatic transfer? | Required Odoo work | Practical decision | | Custom management reports | No | Rebuild reporting views, measures and access rights | Start with reports used in board packs and month-end review, not every historic printout. | | User permissions | No | Define roles, company access and approval limits | Build access around job responsibilities, not around the users who happened to have Pastel access. | | Approval workflows | No | Configure purchasing, payment and credit controls | Test exceptions, such as an urgent purchase above a manager’s limit. | | Third-party integrations | No | Reconnect payroll, banking, e-commerce, logistics or tax systems | Confirm the data owner, failure alerts and reconciliation method for each integration. | | Invoice and document layouts | No | Configure branded documents and mandatory tax fields | An invoice layout is a compliance document in jurisdictions with fiscalisation or e-invoicing rules. | | Tax mapping and fiscal positions | No | Configure local taxes, customer rules and product treatment | Default localisation settings may require adjustment for the business’s real transactions. | | Stock costing method | No | Select and test the costing approach before opening stock is posted | Changing the approach after go-live can make margin analysis inconsistent. |   Odoo fiscal localisations provide default charts, taxes and fiscal positions. They are a starting point, not a substitute for a tax design review. A multi-entity group may sell across borders, use exempt supplies or operate different branches under different registrations. Those facts determine the configuration.

Compliance must be ready before cutover

Tax compliance cannot be placed on a post-go-live list. Once Odoo becomes the invoicing system, its invoice flow, tax mapping and integrations must meet the requirements that apply to the entity.

●        Zambia: Smart Invoice has applied since 1 July 2024. ZRA states penalties can reach K40,000, then K80,000 and then K120,000, with repeat non-compliance potentially carrying imprisonment of up to three years. The reason to configure before cutover is direct: an operational invoice process that cannot meet Smart Invoice requirements creates immediate exposure.

●        Kenya: KRA requires eTIMS invoices for all businesses. The onboarding notices distinguish key dates of 1 September 2023 and 1 January 2024 for the wider rollout. Unsupported expenditure is non-deductible, so procurement teams need supplier invoice controls as well as sales invoicing controls.

●        Zimbabwe: ZIMRA fiscalisation applies even to taxpayers below the USD25,000 VAT threshold. A business should not assume that falling below the VAT threshold removes fiscalisation work.

●        Nigeria: FIRS Merchant-Buyer e-invoicing has applied from 1 August 2025 to taxpayers with annual turnover of at least N5 billion. For a group near that threshold, assess annual turnover by the relevant taxpayer before approving the solution design.

●        South Africa: SARS confirms the standard VAT rate remains 15% as of October 2026. Do not alter rate tables based on the withdrawn proposed 2025 and 2026 increases.

The practical test is simple. Take a real sale, credit note, supplier bill, stock receipt and payment from each country entity. Run them through the configured Odoo environment and ask whether the tax result, document output and audit evidence are correct. If that test has not happened, the entity is not ready for cutover.

The accounting and inventory controls that protect go-live

A good migration is not proven by the number of rows imported. It is proven when finance can reconcile the opening position and operations can transact without creating unexplained exceptions.

For inventory, Odoo can receive an opening position by product, quantity, location and lot or serial number. The total valuation must reconcile to the inventory balances in the opening trial balance before go-live. This is one of the checks teams skip when stock quantities come from a warehouse export and values come from an accounting report.

If those two sources disagree, stop. Do not post a balancing journal merely to make the trial balance look correct. Find whether the difference arises from unprocessed goods received notes, old adjustments, obsolete stock, a costing-method issue or a count variance. Otherwise, the first month-end in Odoo starts with a number nobody can defend.

Worked example: an illustrative Zambian distributor

Take a Lusaka electrical distributor with 12 staff, two warehouses, about 2,800 stock lines and monthly revenue of roughly K6 million. Its Pastel records show inventory values that differ from the general ledger by K420,000, while sales staff maintain separate customer price lists in spreadsheets. The business wants Odoo Sales, Purchase, Inventory and Accounting, with Smart Invoice configured before cutover.

We would not advise importing five years of sales history into the operational database. The better scope is clean contacts and products, open orders, open invoices and bills, opening stock by location, a reconciled opening trial balance and bank opening balances. The K420,000 difference must be investigated before go-live because an unexplained opening adjustment will distort gross margin and weaken auditability.

The management team would also need to decide who owns price changes and who can release a credit note. In a second implementation, we would bring those approval decisions into the first design workshop rather than waiting for user acceptance testing. That reduces late changes to permissions and document flows.

Worked example: an illustrative Kenyan multi-entity group

Consider a Nairobi-based group with a trading company and a service company, 45 users and a US$40,000 monthly payroll. It uses Pastel for finance, spreadsheets for approvals and separate tools for customer invoicing. The board wants unified visibility, but the finance manager also needs eTIMS-compliant invoicing and separate controls by entity.

The right migration scope is not two copies of the same configuration. Each company needs its own tax treatment, journals, access rules and opening balances, while group reporting needs consistent account mapping. The team should run at least one full rehearsal: extract data, load it with external IDs, reconcile opening balances, process a sample invoice and test the approval path.

If the group has years of unreconciled transactions, importing all historical movements is usually poor ROI. Retain approved historic reports outside the live operating dataset and move the clean opening position plus open operational items. The finance manager should also require a written sign-off showing that stock valuation, receivables, payables, bank balances and the trial balance agree before the production cutover.

How long does a Sage Pastel to Odoo migration take?

There is no official standard duration for a Sage Pastel to Odoo migration. Any provider promising a fixed period before reviewing the data, entities, integrations and country compliance is estimating the least difficult version of the project.

Timeline depends on the volume and quality of data, number of companies, historical transactions retained, integrations, tax compliance, customisation, migration rehearsals and user acceptance testing. A single company with clean master data and limited integrations has a different scope from a five-country group with warehouses, serialised stock and local fiscalisation requirements.

We assess the work in stages rather than attach a calendar promise before discovery.

1.       Discovery and scope definition: identify entities, modules, integrations, tax requirements, data owners and reporting priorities. This stage prevents the project from becoming an unpriced list of legacy requests.

2.       Data extraction and mapping: document each Pastel source, target Odoo field, transformation rule and owner. This is where duplicate customers, inactive products and invalid tax codes become visible.

3.       Configuration and localised compliance: configure the chart, taxes, journals, workflows, document layouts and required e-invoicing or fiscalisation processes. This needs to happen before transaction testing because tax and posting results depend on it.

4.       Test migration and reconciliation: load a controlled dataset, use external IDs, compare totals and correct the mapping. Since imports are permanent, test environments protect the production database from avoidable clutter.

5.       User acceptance testing and training: process real scenarios with finance and operations staff, including returns, credit notes, stock variances and approval exceptions. A system is not ready because the implementation team can operate it.

6.       Cutover and hypercare: freeze agreed legacy activity, load final approved data, validate opening balances and support the first live transactions. The cutover checklist needs named owners and timed sign-offs.

For decision-making, the important question is not “How many weeks?” It is “What must be true before we allow the first live invoice, purchase receipt and payment?” The answer should include reconciled balances, tested tax compliance, trained users and board-approved control ownership.

Frequently Asked Questions

Can we move all Sage Pastel history into Odoo?

Technically, some historic records can be imported, including journal entries and orders. We usually advise against loading years of unreconciled operational history unless there is a clear reporting, legal or audit need. Clean master data, open items and reconciled opening balances normally provide better value and lower implementation risk.

Will Sage Pastel account codes work in Odoo?

They can often be retained or mapped to equivalent Odoo accounts. Do not delete or alter the types of standard Odoo default accounts used by the system. Rename or recode equivalent accounts, then add only the accounts required for valid reporting or compliance.

Can opening inventory be imported from Pastel?

Yes. Odoo can take product, quantity, location and lot or serial number data. Before go-live, the total imported stock valuation must reconcile to the inventory amount in the opening trial balance. Quantity agreement alone is not enough.

Does Odoo automatically handle Smart Invoice, eTIMS or fiscalisation?

No implementation should assume that. Localisation provides default accounting structures, taxes and fiscal positions, but the applicable invoice flow, tax mapping and statutory integration must be configured and tested for the relevant entity. Zambia, Kenya, Zimbabwe and Nigeria each have specific requirements described by their respective authorities.

Sources used for the migration design

Our implementation approach follows Odoo 19 official documentation on upgrades, import and export, accounting setup and opening balances. The country compliance points above are based on official notices and guidance from ZRA, KRA, ZIMRA, FIRS and SARS, current as of October 2026. Regulatory requirements can change, so confirm the final configuration against the entity’s current tax position before production cutover.

If your Pastel environment is carrying unreconciled balances, manual approval workarounds or country-specific invoice obligations, start with the scope before selecting a go-live date. Request a Consultation through our migration to Odoo service.