Migrating a website into Odoo usually stalls on the parts nobody budgeted for: hundreds of website.page records, years of blog content, product descriptions, and — the real killers — the images embedded in rich text, the per-language translations, and the SEO metadata (meta titles, descriptions, canonical URLs, redirects) that protect your search rankings. Odoo native gives you a generic import interface for standard models, but it treats a page as a flat row of data. It does not rehydrate <img> sources into ir.attachment records, it does not map your source CMS's language codes onto res.lang and Odoo's field-translation layer, and it has no concept of preserving old URLs so inbound links and Google's index don't break on cutover day. Teams end up copy-pasting page by page, losing alt text and hreflang along the way, and then watching organic traffic dip after launch.

Website Page Migration is a made-to-order Odoo module that ECOSIRE builds around your specific source system and content shape. At its core is a configurable import engine that reads your exported content (CSV, JSON, XML, WXR, or a direct read from your old CMS over its API) and maps it onto Odoo's real models: website.page and its backing ir.ui.view (QWeb arch) for static pages, blog.post/blog.blog for articles, and product.template/product.public.category for the e-commerce catalog. Rich-text bodies are parsed so that every embedded image is downloaded, deduplicated by checksum, stored as an ir.attachment, and re-referenced with a stable /web/image/... URL — alt text and captions carried across. A staged, transactional loader (with idempotent external IDs in ir.model.data) means a re-run updates rather than duplicates, so you can migrate in waves and re-import safely.

Technically, the module is a proper addon with a versioned __manifest__.py depending on website, website_blog, and (when catalog is in scope) website_sale. Translations are handled by resolving each source locale to an active res.lang, then writing the translated values through Odoo's translation API so the front-end language switcher and hreflang tags work correctly. SEO is first-class: we map source meta titles/descriptions and website_meta_keywords, set canonical hints, and generate website.rewrite (301) records from every old path to its new Odoo URL so link equity and bookmarks survive. Access is governed by ir.model.access.csv plus record rules so the migration wizard is limited to administrators, and the whole run is logged for audit. A wizard (TransientModel) drives mapping, dry-run validation, and a preview report; larger jobs run through queued/automated actions so a 20,000-record import doesn't tie up a worker or hit request timeouts. It targets Odoo 17.0, 18.0, and 19.0, and we note Community vs Enterprise differences up front — e.g. multi-website routing and certain website tools differ, and we build to whichever edition you run.

Because this is build-to-order, nothing ships until we've scoped it with you. A short scoping call establishes your source platform, content volume, languages, and catalog complexity; we then confirm a fixed quote and a field mapping, build the module against a copy of your source data, and validate it on a staging database before touching production. Typical delivery is one working week from confirmed scope, depending on source-data cleanliness and volume. Pricing starts from $999 (indicative, single-company base scope); large data-migration volume, additional source platforms, deep multi-language depth, and multi-company or multi-website routing increase the quoted scope. You receive the installable source, so you are never locked to us.