Starting with Odoo 19, all VentorTech e-commerce connectors use a new job backend called Integration Queue Job (integration_queue_job), replacing the older OCA queue_job.
When upgrading from Odoo 16 / 17 / 18 → Odoo 19, additional steps are required to avoid data loss or upgrade errors – especially on Odoo.sh.
This guide explains exactly what to do, why it is required, and how to complete the migration safely even for non-technical users.
Why Extra Migration Steps Are Required
Most customers currently have these modules installed:
Odoo E-Commerce Connector Core module (integration)
Shopify (integration_shopify), WooCommerce (integration_woocommerce), Magento (integration_magento2) or PrestaShop (integration_prestashop) module(s)
Job Queue (queue_job)
(Optional) Job Queue Subscribe (queue_job_subscribe)
But in Odoo 19.0:
The old modules (queue_job, queue_job_subscribe) no longer exist
They cannot be simply uninstalled without destroying connector data
The Odoo Upgrade Service runs without custom modules, so migration scripts cannot run there
If the upgrade is attempted “as is”, you will get:
Orphaned job tables
Duplicated job channels
Missing models
Connectors failing on startup
To solve this, we use shim modules.
What Are Shim Modules?
Shim modules are small compatibility modules that:
Keep the module names queue_job and queue_job_subscribe installed
But contain no models and no data
Simply depend on our new module integration_queue_job
This allows:
The Odoo Upgrade Service to safely load the migrated DB
Odoo 19.0 to continue seeing the old modules as “present”, avoiding uninstall operations
Our new backend to replace the old one transparently
Shim modules are needed only during the migration and can be removed later.
What You Need Before Starting
Latest version of our e-commerce connectors code deployed to production
Ensure your project is on the latest version of:
VentorTech connectors for your current Odoo version
Any custom connector extensions
Step-by-Step Migration Instructions (Odoo.sh)
This section is intended for customers and implementation partners.
STEP 1. Ensure Production is Healthy
On your Odoo.sh Production branch:
Update to the latest VentorTech connector versions for your current Odoo version
Ensure all modules install correctly
Fix any failing builds
Verify connectors work (import order, sync product, etc.)
A clean Production environment is essential because this is the database the upgrade service will use.
STEP 2. Create and Prepare an Odoo 19 Migration Branch
This method ensures a clean migration without causing build failures on Odoo.sh.
Create a new branch from Production
Name it anything, e.g. 19.0-migration
Do NOT switch the branch to Odoo 19 yet
Why not switch now?
Because the branch would try to build Odoo 19 with Odoo 18 modules still present – causing errors. We avoid this by preparing all code before the version switch.
Replace all modules in newly created branch with their Odoo 19 versions. Make sure to add integration_queue_job module instead of queue_job module.
This step is purely Git-level changes – you are preparing the final 19.0 codebase.
Add the shim modules. These must be manually added to the same branch:
queue_job (shim – always required):
queue_job_subscribe (shim – only if it was installed previously):
The shim modules contain:
No models
No data files
Only a dependency on integration_queue_job
Their purpose is to keep the upgrade service from trying to uninstall old queue_job modules (which would break connector data). You may distribute ZIPs for customer convenience.
Commit and push.
At this point your branch:
Still shows as “Old version”
Contains fully prepared Odoo 19.0 code
Includes the shim modules
Is ready for the upgrade process
This is exactly what we want.
Frequently Asked Questions
Q: Do I need to remove OCA queue_job manually?
No – never do this. The shim modules replace it safely.
Q: Why does the upgrade log say “module queue_job: not installable, skipped”?
This message comes from the Upgrade Service, which does not include your custom shim modules. It is normal and expected.
Q: What if I won’t add the shim modules before upgrade?
The upgrade will fail. Always ensure the migration branch includes them.
Q: Can shim modules be used for future upgrades?
They are needed only for the upgrade to Odoo 19. After the system stabilizes, they can be removed.
Q: Why can’t the upgrade happen automatically?
Because Odoo’s upgrade platform:
Cannot load custom modules
Cannot remove models added by legacy Job Queue (queue_job) module without their Python classes
Would destroy connector data without transitional logic
Shim modules solve this cleanly.
Need help or have questions?
If you need assistance preparing your migration branch, adding shim modules, or validating your upgraded environment, our support team is here to help.
đź“© Reach out to our support team: Support Portal