Bulk Catalog Import / Migration Toolkit

Key Features

Source connectors for Shopify (Admin REST/GraphQL), Magento 2 REST, WooCommerce WC REST and generic CSV/Excel, each normalizing into one shared staging model

Variant reconstruction that maps source option matrices onto product.template plus product.product with correct product.attribute / product.attribute.value combinations

Attribute mapping wizard (OWL) to bind, merge, split or rename source options before any write to the live catalog

Category and tag taxonomy remapping from source collections onto product.category and product tags, including nested hierarchies

Streaming image ingestion with SHA-based de-duplication, attached to the correct template or variant rather than a single image field

SEO preservation: capture source handles/URLs, generate canonical Odoo slugs, and map meta title/description/OG onto the website.seo.metadata mixin

301 redirect plan emitted for website.rewrite or your reverse proxy so old URLs keep their ranking equity through cutover

Dry-run mode producing a full create/update/skip diff report as QWeb PDF/HTML before a single record is written

Idempotent, re-runnable imports keyed on a stable external reference so repeated runs update instead of duplicating

Configurable validation rules (missing price, invalid variant matrix, oversized/broken images, encoding issues) that block bad rows early

Batched, transactional commits with correct recomputation of @api.depends compute fields and proper unit-of-measure/price handling

Rollback that cleanly restores prior state when a batch fails validation, so nothing is left half-migrated

Row-level import logs and error export so failed records can be corrected and re-run without touching successful ones

XML-RPC/JSON-RPC and scheduled-action (ir.cron) hooks for incremental delta syncs during a phased cutover

Access controlled via ir.model.access.csv plus record rules so only migration operators can run jobs, scoped by company

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Moving an established online store onto Odoo eCommerce is where most migrations quietly go wrong. Your source catalog holds thousands of SKUs with option-based variants, multiple image sizes, rich HTML descriptions, nested collections and years of accumulated SEO equity — and Odoo's stock base_import wizard treats all of it as flat rows. It has no concept of mapping a Shopify option matrix onto product.template + product.product with the right product.attribute / product.attribute.value combinations, no image ingestion beyond a single field, no taxonomy remapping, and absolutely no plan for the 301 redirects that keep your Google rankings alive. Do it by hand and you get duplicated variants, broken website.slug URLs, orphaned images and a support queue full of "where did my product go" tickets.

The Bulk Catalog Import / Migration Toolkit is a purpose-built Odoo module (proper __manifest__.py, models extending models.Model, security via ir.model.access.csv + record rules, OWL/QWeb wizard UI) that ECOSIRE builds around your exact source data. It ships source connectors that read Shopify (Admin REST/GraphQL), Magento 2 (REST), WooCommerce (WC REST) and generic CSV/Excel, and normalizes each into a staging model before anything touches your live catalog. A mapping wizard lets you bind source option names to Odoo attributes, collapse or split variants, and remap source collections/tags onto product.category and product tags. Images are streamed in with de-duplication and attached to the correct template or variant, not dumped into one field. Every run is transactional and idempotent — records are matched by a stable external key so re-running updates rather than duplicates.

Technically, the toolkit runs as a job: extract to a staging table, validate against configurable rules (missing prices, invalid variant matrices, oversized images, encoding issues), then commit into product.template/product.product in batches with compute fields (@api.depends) recalculated correctly. A dry-run mode produces a full diff report (QWeb PDF/HTML) showing exactly what will be created, updated or skipped — before a single write. SEO preservation is first-class: source handles/URLs are captured, a canonical Odoo slug is generated, and a 301 redirect plan is emitted (loadable into Odoo's website.rewrite or your reverse proxy) so old URLs and their link equity survive the cutover. Meta titles, meta descriptions and OG data map straight onto the website.seo.metadata mixin. If a batch fails validation, rollback restores the prior state cleanly — nothing is left half-migrated.

Because this is build-to-order, ECOSIRE first runs a short scoping call to inspect a sample of your real export, agree the field/attribute mapping and confirm the target Odoo edition (Community vs Enterprise) and version (17.0, 18.0 or 19.0). We then build and unit-test the connectors against your data, run a full UAT migration on a staging database, hand you the diff report and 301 plan for sign-off, and only then execute the production cutover. Typical delivery is 2–4 weeks from confirmed scope depending on catalog size and how clean the source data is. You receive the installable module source, a git repository, documentation and a post-go-live support window — no marketplace download, no guesswork, a migration that actually lands.

What you get

Installable Odoo module source code targeting your confirmed version (17.0, 18.0 or 19.0) and edition (Community or Enterprise)

Installation, configuration and connector-credential setup on your staging and production databases

Technical documentation: data model, field/attribute mapping spec, connector config and validation-rule reference

End-user guide plus a live training session for the operators running migration jobs

UAT migration executed on a staging database with the diff report and 301 redirect plan for your sign-off before cutover

Rollback and cutover runbook covering batch failure, re-run and go-live sequencing

Git repository handover with full commit history and tagged release

Post-go-live support window for defect fixes and mapping adjustments after the production migration

Who this is for

Store owner replatforming to Odoo

Runs an existing Shopify, Magento or WooCommerce store and is consolidating onto Odoo eCommerce + ERP. Needs the full catalog — variants, images and SEO — moved without losing rankings or duplicating products.

Odoo implementation partner / integrator

Delivering an Odoo project where catalog migration is on the critical path. Wants a proven, re-runnable importer with dry-run and rollback instead of hand-writing base_import scripts for each client.

eCommerce / operations manager

Owns catalog data quality and the go-live cutover. Needs validation, a preview diff and a documented 301 plan to defend organic traffic and sign off the migration with confidence.

IT / systems administrator

Responsible for the Odoo environment and connector credentials. Needs clean access control (ir.model.access.csv + record rules), scheduled delta syncs and a git-tracked module they can maintain.

How Bulk Catalog Import / Migration Toolkit Compares

Criterion	ECOSIRE	Custom Build	Competitor
Source platform coverage	Shopify, Magento 2, WooCommerce, CSV/Excel connectors built and tested against your data	Whatever you find time to build, usually one source	Often a single format or generic CSV only
Variant reconstruction	Maps option matrices onto template + variants with correct attribute values	Manual, error-prone mapping per project	Basic; complex matrices often duplicate or break
SEO & 301 redirects	URLs, meta and OG preserved with a generated 301 plan	Only if you scope and build it yourself	Rarely handled; SEO usually lost
Dry-run & validation	Staging + validation rules + create/update/skip diff report	Depends on effort invested	Limited preview, minimal validation
Rollback safety	Transactional batches with clean rollback on failure	Must be engineered from scratch	Usually absent
Re-runnable / idempotent	Keyed on external reference — re-runs update, never duplicate	Rarely built idempotent under deadline	Often duplicates on re-run
Version & edition fit	Built for your exact Odoo 17/18/19 and Community/Enterprise	Whatever you target	May lag Odoo releases
Support & handover	Post-go-live window, docs, training and git repo handover	Internal only	Ticket-based, generic

Frequently Asked Questions about Bulk Catalog Import / Migration Toolkit

How long does delivery take?

Because this is build-to-order, we build the connectors against your actual export rather than shipping a generic download. After a short scoping call and mapping sign-off, typical delivery is 2–4 weeks from confirmed scope, depending on catalog size and how clean the source data is. Very large or messy catalogs may extend this, and we tell you before you commit.

Which source platforms can you migrate from?

Out of the toolkit design we support Shopify (Admin REST/GraphQL), Magento 2 (REST), WooCommerce (WC REST) and generic CSV/Excel. If your source isn't listed, we can usually add a connector during scoping as long as it exposes an API or a structured export.

Will my SEO and existing URLs survive the migration?

Yes — that is a core reason the toolkit exists. We capture your source handles/URLs, generate canonical Odoo slugs, map meta title/description/OG data onto Odoo's website.seo.metadata mixin, and emit a 301 redirect plan you load into Odoo's website.rewrite or your reverse proxy so old URLs keep their ranking equity.

What happens if the import goes wrong?

Nothing touches your live catalog blind. Every run stages data first, validates it against configurable rules, and offers a dry-run diff report before writing. Commits are batched and transactional, and a failed batch rolls back cleanly so you are never left with a half-migrated catalog. We also run a full UAT migration on staging before production.

Does it work with Odoo Community or only Enterprise?

Both. We confirm your edition during scoping and build accordingly. The core migration engine relies on standard Odoo models (product.template, product.product, product.attribute, product.category) available in Community; any Enterprise-only touchpoints in your target are handled explicitly rather than assumed.

Which Odoo versions are supported?

We build for Odoo 17.0, 18.0 and 19.0. You tell us your target version at scoping and we deliver the module built and tested against exactly that version — no forward/backward guesswork.

What support and updates do I get after go-live?

Delivery includes a post-go-live support window for defect fixes and mapping adjustments, plus the full git repository so your team can maintain it. Beyond the included window, ECOSIRE offers ongoing support and can extend connectors or add delta-sync automation as your catalog evolves.