How hard is the Odoo 14 to 15 migration?

Moderate difficulty for standard installations. The payment module rewrite is the biggest challenge — any custom payment integrations need complete rewriting. If you only use standard payment providers, the migration is relatively straightforward.

Can I skip Odoo 15 and go directly to a newer version?

Yes. Odoo's migration service and OpenUpgrade support multi-version jumps. However, you still need to handle the payment module architecture change regardless of target version, as all versions from 15 onward use the new system.

What happened to payment_ingenico?

payment_ingenico was replaced by payment_ogone in Odoo 15. If you used Ingenico, you need to reconfigure with the new Ogone module. The underlying provider API is similar but the Odoo module architecture is completely different.

Do I need to update Python for Odoo 15?

Odoo 15 requires Python 3.7 or higher. If you are running v14 on Python 3.6, you need to upgrade Python as part of the migration. Python 3.10 is recommended for best compatibility.

Odoo 14 to 15 Migration Guide: Payment Module and Breaking Changes

Overview

Migrating from Odoo 14 to 15 primarily involves adapting to the payment module rewrite and handling new module additions. This guide covers the breaking changes, migration strategy, and common issues encountered during the upgrade.

Payment Module Rewrite

The most significant breaking change in Odoo 15 is the complete rewrite of the payment module. The old payment.acquirer model is replaced with a new payment.provider architecture.

Key Changes

payment.acquirer model renamed/restructured as payment.provider
Transaction flow standardized with new state machine
Webhook handling completely rewritten
Provider-specific code moved to dedicated modules
Token management system overhauled

Impact on Custom Payment Integrations

Any custom payment acquirer built on v14's payment.acquirer model must be rewritten from scratch. The new architecture is cleaner and more standardized, but there is no direct mapping from old to new code. Budget significant development time for this.

New Modules to Consider

Gift Cards — gift_card, pos_gift_card, sale_gift_card, website_sale_gift_card
Event Booths — event_booth, event_booth_sale, website_event_booth
Project Bridges — project_account, project_purchase, project_hr_expense
GS1 Barcodes — barcodes_gs1_nomenclature
Work Entries — hr_work_entry_contract, hr_work_entry_holidays

Removed Modules

procurement_jit — just-in-time procurement removed
adyen_platforms — Adyen for platforms
sale_timesheet_edit, sale_timesheet_purchase
website_form — merged into core
website_mail_channel, website_sale_management
payment_ingenico — replaced by payment_ogone
payment_odoo_by_adyen, payment_adyen_paybylink

Migration Steps

Audit all custom modules for payment.acquirer references
Rewrite custom payment integrations for the new provider architecture
Review project-related customizations against new bridge modules
Check if custom gift card or coupon logic overlaps with new modules
Update Python version if needed (v15 requires 3.7+)
Test all eCommerce and POS payment flows thoroughly

Common Issues

Payment tokens not migrating correctly
Webhook URLs changing for payment providers
Coupon module conflicts with gift card additions
Project accounting customizations conflicting with new bridge modules

DeployMonkey Advantage

DeployMonkey handles Odoo version management and can assist with migration from v14 to current versions. Our platform ensures payment providers are correctly configured on the target version.