Skip to Content

Oracle to Odoo Migration | Professional Data Migration Platform | Schema Introspection · Mapping Engine · 8 EBS Templates · Dry-Run · Resumable

by
Odoo

$ 120.00

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 2282
Technical Name mn_oracle_migration
LicenseOPL-1
Websitehttps://github.com/moaaznaabilali
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 2282
Technical Name mn_oracle_migration
LicenseOPL-1
Websitehttps://github.com/moaaznaabilali
Oracle to Odoo Migration Platform for Odoo 19
PROFESSIONAL ORACLE EBS → ODOO MIGRATION · v19.0.1

Move off Oracle. Without burning your data on the way out.

A complete data-migration platform for moving from Oracle E-Business Suite (or any Oracle 11g / 12c / 19c database) into Odoo. Connect, introspect the schema, map columns to Odoo fields, transform, validate, dry-run, execute in resumable batches, and verify with a per-row error log. Eight pre-built Oracle EBS templates included — Customers, Vendors, Items, GL accounts, AR invoices, AP invoices, Sales orders, HR employees.

Connect. Map. Validate. Dry-run. Execute. Resume.

$120 · ONE-TIME · OPL-1
★ HOW IT WORKS · EIGHT STEPS ★

From "I have an Oracle database" to "data is in Odoo".

STEP 1
Connect to Oracle
Configure host / port / service_name or SID / user / password. Thin mode — pure Python, no Oracle client install required. One click "Test connection" returns the Oracle version banner.
STEP 2
Introspect schema
Auto-discover schemas, tables, columns, data types, primary keys, foreign keys via ALL_TABLES / ALL_TAB_COLUMNS. Cached locally so you can browse even when Oracle is offline.
STEP 3
Pick a template
8 pre-built Oracle EBS → Odoo templates included: Customers · Vendors · Items · GL · AR · AP · Sales Orders · HR Employees. Each template ships with the column-by-column mapping ready to apply.
STEP 4
Map columns to fields
Per-mapping transformer — upper, lower, strip, to_int, to_float, to_bool, oracle_date_to_iso, digits_only, country_code_to_id, currency_code_to_id, or your own Python expression.
STEP 5
Validate
Pre-flight checks — required fields, type compatibility (target field exists on the Odoo model), foreign-key resolution, duplicate detection. Errors surfaced before any data is touched.
STEP 6
Dry-run preview
Fetch the first N rows from Oracle, run the full transformation pipeline, show the resulting Odoo records as JSON. Nothing committed. Verify the mapping is correct before going live.
STEP 7
Execute in batches
Chunked import (default 500 rows / batch). Checkpoint commit per batch. Resumable — if the migration is interrupted, restart from the last successful offset. Each row gets an external_id so re-runs UPDATE instead of duplicating.
STEP 8
Verify + re-run failed
Per-row success/failure log with the exact error message. Export failed rows to CSV, fix in Excel, re-run failed-only — no need to re-process the successes.
★ LIVE OPS DASHBOARD ★

Watch the migration in flight.

7 KPI tiles · click-to-open jobs with progress bars · recent errors list with the source-row preview. Auto-refresh every 15 seconds.

00 — Migration ops dashboard
PROJECTS & JOBS

One project. Many jobs. Dependency order.

01 · MIGRATION PROJECTS
01 — Projects list
02 · PROJECT FORM — nested jobs with row counts + progress
02 — Project form
CONNECTIONS

Oracle, the safe way.

03 · CONNECTIONS LIST
03 — Connections list
04 · CONNECTION FORM — thin / thick mode · service_name OR SID · one-click test
04 — Connection form
8 PRE-BUILT TEMPLATES

Oracle EBS → Odoo, ready to apply.

05 · TEMPLATES KANBAN — grouped by category
05 — Templates kanban
06 · TEMPLATE FORM — suggested mapping in JSON · one-click "Create job from this template"
06 — Template form
THE JOB — the heart of the platform

Source · target · mapping · runs · failed rows.

07 · JOBS LIST — progress bar + row totals + state
07 — Jobs list
08 · JOB FORM — column mapping editor with transformer + Python expression + idempotency key
08 — Job form
EXECUTION + AUDIT

Every run logged. Every row traceable.

09 · RUN HISTORY — duration · batches · success rate
09 — Run history
10 · TRANSFORMERS — 12 reusable functions + your own Python expressions
10 — Transformers
11 · ALL MAPPINGS — column-level view across every job
11 — All mappings
EVERYTHING IN THE BOX

30+ features. 9 models. 8 templates. 12 transformers.

🔌 ORACLE 11g/12c/19c
Thin-mode python-oracledb — pure Python, no Oracle Instant Client install. Thick mode supported when you need OCI features.
📁 CSV FALLBACK
When Oracle isn't reachable from the Odoo server, upload a CSV export of any table and use the same mapping pipeline.
📋 8 EBS TEMPLATES
Customers (HZ_PARTIES) · Vendors (AP_SUPPLIERS) · Items (MTL_SYSTEM_ITEMS_B) · GL (GL_CODE_COMBINATIONS_KFV) · AR (RA_CUSTOMER_TRX_ALL) · AP (AP_INVOICES_ALL) · SO (OE_ORDER_HEADERS_ALL) · HR (PER_ALL_PEOPLE_F).
⚙ 12 TRANSFORMERS
identity · upper · lower · strip · to_int · to_float · to_bool · oracle_date_to_iso · digits_only · default_if_empty · country_code_to_id · currency_code_to_id.
📝 PYTHON EXPRESSIONS
Per-mapping inline Python — overrides the transformer when set. The raw value is bound to v. Example: v.replace('-', '').upper().
🎯 IDEMPOTENT
Each row pairs the source unique key with an ir.model.data row. Re-runs UPDATE existing records — never duplicate.
⏳ RESUMABLE
Checkpoint commit per batch. If interrupted, the next "Run" picks up from last_progress_offset. Survives crashes, timeouts, restarts.
📹 DRY-RUN PREVIEW
Fetch the first 5 rows, run the full pipeline, render JSON of the resulting Odoo records. Zero commits.
📊 LIVE DASHBOARD
OWL component. 7 KPI tiles, jobs grid with progress bars, recent errors. Auto-refresh every 15 seconds.
🔗 DEPENDENCY ORDER
Multi-job dependencies via parent_job_ids. Parents finish first — orchestrate Customers → Invoices, Items → Stock, etc.
💾 MAPPING JSON I/O
Export the current mappings as JSON for version control. Import JSON from a previous project to reuse mappings.
⚠ PER-ROW ERROR LOG
Every failed row gets a mn.migration.line with the exact error + source-row preview. Filterable, exportable.
🔎 SCHEMA INTROSPECTION
Auto-discover via ALL_TABLES / ALL_TAB_COLUMNS. Browse schemas, tables, columns. Pick fields to map.
🔨 WHERE CLAUSE FILTER
Optional SQL fragment applied to source SELECT. Migrate only the rows you care about — e.g. STATUS = 'A'.
🏮 BATCH SIZE
Per-job batch size. Default 500. Increase for raw speed, decrease for memory-constrained Oracle servers.
⚙ 2 SECURITY GROUPS
User (read + run) vs Admin (CRUD connections + templates + transformers + delete runs).
📐 ANY ODOO MODEL
Target field validated against self.env[target_model]. Migrate into any Odoo model — built-in OR custom.
🧮 FORWARD-COMPATIBLE
Pure Python, no native deps beyond optional python-oracledb. Works on any Odoo host.
WHAT YOU GET FOR $120

A migration consultant for the cost of an hour of one.

9 models (connection · transformer · template · project · job · mapping · run · line · dashboard) ~$1,800
Oracle driver wrapper with thin/thick mode + introspection ~$1,000
12 reusable transformers + Python-expression evaluator ~$600
8 pre-built Oracle EBS templates with column-by-column mappings ~$2,400
Resumable batched importer with per-batch checkpoint commit ~$1,200
Idempotent UPSERT via ir.model.data + re-run-failed-only ~$800
Dry-run preview wizard ~$400
OWL live dashboard with auto-refresh + click-to-open ~$900
Mapping JSON export/import for version control ~$300
Per-row error log + CSV export of failed rows ~$400
Source code · 2 security groups · lifetime updates · OPL-1 ~$400
Bespoke equivalent ≈ $10,200 Your price: $120

$120.

Install in ten seconds.

Install for $120 →
ORACLE → ODOO MIGRATION · v19.0.1.0.0 · OPL-1

Built by Moaz Nabil · moaaznaabilali@gmail.com

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.