Integrators quoting migrations
Every week somebody asks for an upgrade quote. With the radar you quote from numbers instead of guessing, and you decide which modules are worth repairing and which are worth replacing.
Odoo upgrade radar
Know what breaks before you ask for an upgrade quote.
Odoo ships a version every year, and custom code breaks in ways nobody sees until it runs. Before you contract the migration to Odoo 19, the radar walks through your modules and returns, within 48 hours, what breaks, in which file and on which line, how to fix it, the order worth doing it in, what is cheaper to replace with an OCA module already migrated, and how many hours the whole thing takes.
From USD 290, report in 48 hours.
Measured on 20 public repositories and 1,321 modules. What breaks, and how often.
Who it is for
Companies running Odoo with custom code
One or two versions behind, with code nobody wants to touch. The radar says what catching up costs, so you can ask for a quote knowing what you are talking about, or decide with numbers that this year is not the year.
Before signing a migration
A full map with file and line is what a vendor should hand you and almost never does. Use it to ask that their proposal answers every point.
What you get
Every finding with file and line
Not "the views need a review": the file, the line, the excerpt, and what happens if it stays as it is.
Severity and order
First what stops the module from loading, then what breaks a flow, and technical debt last or never.
Replace instead of repair
Which modules already have a migrated equivalent in the OCA: replacing usually costs less than fixing.
Effort in hours
Mechanical work and work that needs testing and data, per module and in total, so you can budget without guessing.
Evidence, not opinion
Every rule in the catalogue cites where it was verified in the Odoo 19 source. When somebody asks why, there is a line to point at.
English or Spanish
The report comes in your language, as a PDF, within 48 hours of payment and access to the repository.
Price by size
The price depends on the one thing you can check before paying: how many modules the repository holds. A single payment, no subscription.
Up to 15 modules
A small repository, or a client with few customisations.
16 to 60 modules
The common case: the customisation base of one company, or of an integrator's client.
More than 60 modules
Large repositories, or several clients in one. Above two hundred modules it is quoted individually.
The first three clients get 20 % off in exchange for permission to cite the result without naming the company. Full refund within fourteen days, under the refund policy.
How it works
01
Ask for the report
With the repository link, public or with read access, and the target version.
02
Pay up front
A one-line quotation with the tier that applies, and online payment from your portal.
03
Get the PDF in 48 hours
By email and in your client portal, in English or Spanish, with the invoice.
04
Decide with numbers
Ask for the quote knowing what breaks, or decide that this year is not the year. And if you want AI to do the migration under supervision, that is the next step up.
05 /
Request the report
Leave the repository link and the target version. I reply with the quotation for your tier within one business day; the report ships 48 hours after payment.
contacto@andresbrinez.comYour repository is read under written rules: read-only, used only for the report and deleted 30 days after delivery. Radar confidentiality.