Question 1

Which systems can you migrate from?

Accepted Answer

Zoho Books, CRM and Inventory, Tally ERP 9 and Prime, ERPNext v13 and above, and any system that can produce Excel or CSV exports. In-house and legacy builds are handled expert-led, working from database dumps or exports.

Question 2

What data actually moves?

Accepted Answer

Customers, vendors, products, chart of accounts, stock on hand, open invoices, open sales and purchase orders, and historical transactions. You choose the sets, and each one is mapped to a named Odoo model before anything loads.

Question 3

Can we migrate in phases?

Accepted Answer

Yes. Master data first, then open documents, then history. Each phase is a separate load run against the same mapping, so nothing has to be re-scoped between phases.

Question 4

Do you migrate attachments and documents?

Accepted Answer

Invoice PDFs, contracts and product images move when your source system exposes them. Files stored outside the ERP, such as a shared drive, are linked rather than imported unless you ask for a bulk upload.

Question 5

What is the difference between API and expert-led?

Accepted Answer

With API access we pull data directly from your live system with read-only credentials, which suits current, online sources. Expert-led means a specialist works from your exports or temporary access, cleans and maps the data, and validates it with you. Excel, in-house and unlisted systems are always expert-led.

Question 6

How long does a migration take?

Accepted Answer

Master data only, on an API source, typically completes in two to five working days. A full migration with history, open documents and reconciliation runs three to six weeks, most of which is validation and sign-off rather than loading.

Question 7

Do we need to stop working during the migration?

Accepted Answer

No. Test loads run against a staging database while you keep working in the old system. Only the final delta load needs a freeze window, usually a weekend, after which the old system goes read-only.

Question 8

Can we see the data before go-live?

Accepted Answer

Every migration includes a staging database you can open and click through. You reconcile counts, trial balance and stock valuation there, and go-live only happens once you sign off.

Question 9

How is the fee calculated?

Accepted Answer

One fixed fee per migration, scoped from your record volume and the number of data sets. The fee is confirmed after the data audit and does not change mid-project.

Question 10

Does the fee include the Odoo subscription?

Accepted Answer

No. Odoo bills apps and users directly. We quote only the migration work, so the two invoices stay separate and auditable.

Question 11

What if the record count is higher than estimated?

Accepted Answer

Counts are confirmed during the data audit, before any load runs, and the fee is fixed at that point. If your data turns out larger than the initial estimate, you see the revised number before work starts.

Question 12

Is a trial or pilot available?

Accepted Answer

Yes. A single data set loaded into a staging database is a common starting point. It is billed as a pilot and credited against the full migration fee if you continue.

Question 13

What happens to duplicate or broken records?

Accepted Answer

Duplicates, missing tax IDs and orphaned references are flagged in a data audit report before loading. You decide per case whether to merge, fix at source, or migrate as-is with a note.

Question 14

How do you prove the migration is correct?

Accepted Answer

Record counts are reconciled set by set, and financial data is checked against your closing trial balance and stock valuation. The result is a validation report you keep for audit.

Question 15

Can we trace a record back to the old system?

Accepted Answer

Every migrated record carries its source reference, so any row in Odoo can be matched to its original in the source system after go-live.

Question 16

How is our data handled?

Accepted Answer

Credentials are read-only, encrypted at rest and revocable at any time. Exports and staging databases are held in an isolated environment and deleted on request once the migration is signed off.

Question 17

Who can see our data?

Accepted Answer

Only the specialists assigned to your migration. Access is logged, and every event in your project is visible in your dashboard event log.

Question 18

What happens to the old system?

Accepted Answer

It stays read-only for reference for as long as you need it. Nothing is deleted at our end, and no writes are made back to the source at any point.

Question 19

What support do we get after go-live?

Accepted Answer

Thirty days of post-migration support covering data corrections, mapping adjustments and user questions, raised as tickets from your dashboard and answered by the specialist who ran your migration.

Question 20

Can you fix something migrated incorrectly?

Accepted Answer

Yes. Corrections within the agreed scope are covered by post-migration support. Because every record keeps its source reference, a bad set can be reloaded without touching the rest of the database.

Questions about migrating to Odoo