Skip to Content

Odoo Test Database: Restore, Neutralise, Verify (2/8)

Build a faithful copy of production to test everything safely.
November 17, 2026 by
ANOR, Cyrille de LAMBERT

In brief A faithful Odoo test database is built in four steps: restoring the dump with its filestore, neutralising the copy to disable all external communication, verifying conformity with production and documenting known differences. Without neutralisation, a copy can send real payment reminders to real customers.

Why your test database must truly mirror production

In episode 1 of the Migration Journal, you took stock of your Odoo instance. Before going further, you need a practice ground: a copy of production where you can break everything without a single customer receiving a message.

An approximate test environment creates two types of problem. First problem: missing data distorts your tests. Second problem: active connectors trigger real actions outside your control.

The goal is straightforward: obtain an inert and identifiable copy that is structurally identical to production. Episode 3 will cover the module audit; for now, focus on the database itself.

Step 1: restore the full copy, database and filestore

Export a complete dump of the production database. A database dump alone is not enough: without the associated filestore, all attachments will appear as missing during verification.

Transfer the SQL dump and the filestore directory together to the test environment. Restore them in one operation, making sure the paths match.

  • Verify that the restored filestore contains the same sub-folders as the production one.
  • Name the test database clearly so it can never be confused with production.
  • Record the exact date and time of the dump: production keeps evolving while you test.

Step 2: neutralise the copy without exception

Neutralisation is the most important operation in this step. It makes the copy inert: no automatic action can reach the outside world.

Odoo offers several ways to neutralise. At restore or duplication time, use the -n flag with the db load or db duplicate commands. You can also tick the dedicated checkbox in the database manager, or run the neutralize command on an already-restored database.

The verified effects in Odoo 20 are as follows:

  • Outgoing mail servers are disabled and their credentials cleared; a dummy server labelled "neutralization - disable emails" replaces them.
  • All scheduled tasks are disabled, except for automatic clean-up.
  • Webhooks are neutralised.
  • An indicator flags the database as neutralised.
  • A "Database neutralized for testing" banner is displayed in the interface.

If your instance uses electronic invoicing exchange modules, check that they have their own neutralisation logic. This is essential: some invoicing connectors can continue communicating with an external platform even after a standard neutralisation.

API keys and payment gateways: neutralisation does not cover all of them. Systematically replace any active API keys with the test values provided by each provider. A live payment key on a test copy remains a live payment key.

Step 3: verify that the copy is faithful to production

A restored and neutralised copy must still conform to production. Go through this checklist before declaring the environment ready.

  • Installed modules: the list must be identical to production.
  • Users: the count and profiles must match.
  • Accounting balances: compare a recent period between the copy and production.
  • PDF invoices: open a few documents to confirm the rendering is correct.
  • Stock: check at least one warehouse.
  • Attachments: open an attached file on any record.
  • Scheduled tasks: confirm they are all inactive.

Some synchronisations, in particular connected calendar and email, only exist on production. Do not look for them on the copy: note their absence as an expected difference rather than an anomaly to fix.

To learn more about how ANOR organises test environments throughout a project, visit the Odoo integrator page.

Step 4: document the copy and its known differences

Production changes every day. A copy frozen at dump time diverges immediately. Documenting this reality saves you from costly confusion during testing.

Record in a shared document:

  • The exact date and time of the dump.
  • Known differences from production (missing synchronisations, replaced keys).
  • The people authorised to access this environment.
  • The planned refresh frequency for the copy.

The practical rule is this: refresh the copy from production before each training or acceptance-testing cycle. A copy that is several weeks old no longer reflects reality and wastes your team's time.

Need methodological support in structuring your environments? Our Odoo support team guides migration projects at every step.

What you have at the end of this step

You now have a complete Odoo test database that faithfully mirrors production, is inert towards the outside world and is fully documented. A concrete example: before this step, a poorly neutralised production copy sends real payment reminders to real customers. After these four steps, the copy displays the neutralisation banner, contacts no external server and carries a reference date known to the whole team.

Episode 3 of the Migration Journal will cover the audit of installed modules: which ones are maintained and which ones pose a risk before the version upgrade.

Want to check whether your Odoo instance is ready for a migration? Request a free audit: an ANOR consultant will analyse your situation and highlight the priority points to address.

in Blog
ANOR, Cyrille de LAMBERT November 17, 2026
Share this post
Tags
Our blogs

A question about your project? Talk to a consultant.

Book 30 minutes