Other AI tools can’t understand your Odoo code and data.ERPeek can.

HubSpot contacts → your live Odoo, in one pass

Consolidating three separate tools into one unified system is exactly what Odoo excels at. The critical thing is importing in the right order, sales and project records reference contacts and products, so those must exist in Odoo first. Contacts are the correct starting point, and since you attached the export, I've already processed it.

What I did with your file

1. Read all 25,412 rows from the HubSpot export and mapped every column to the corresponding res.partner field (18 mapped automatically, 3 via your custom field labels).
2. Deduplicated on email, found 2,813 duplicates from contacts existing in multiple HubSpot lists, merged them keeping the most recent record.
3. Converted to Odoo's import format, companies first, then contacts linked to their company, with country codes and tags normalized to your Odoo 18 configuration.

The rest of the migration, in order

1. QuickBooks → Chart of Accounts & Products, import your account structure first, then products/services with their QB item codes. Tax mappings need manual review, QB stores tax as a flat amount per line while Odoo uses fiscal positions and tax groups. Rebuild the rules, don't import them.
2. QuickBooks → 3 Years of Invoice History, ~420k invoice lines. Import as posted journal entries, do not trigger payment workflows or stock movements. Then post an opening-balance entry matching your QB trial balance on the cutover date, or your accounting will be off from Day 1.
3. Asana → Projects & Tasks, 400 projects. Map Asana boards to Odoo project stages, match members by email. Budget extra time for attachments, they typically run 3-5x the task count in files.
4. Validate & Reconcile, compare totals across all 3 source systems vs. Odoo before cutting over. Realistic timeline for this volume: 2 weeks of preparation, 1 week of test imports, then 3-4 days for the production run with all sources read-only.

Here's your converted, deduplicated import file:

Your project has a live Odoo connection, so I can create these records directly. Nothing is written until you approve:

Route Conflict, Manufacture + Dropship

This is one of the most common, and most confusing, issues in Odoo inventory configuration. When multiple routes are assigned to a product, Odoo doesn't choose the "best" one. It evaluates all active routes simultaneously when a sale order is confirmed, which is why you're seeing both a manufacturing order and a dropship purchase created at the same time.

What's happening now

When a sale order is confirmed for your product, Odoo fires both the Manufacture and Dropship procurement rules at the same time. This creates a manufacturing order that consumes components from your stock AND a purchase order that ships directly from the supplier, double fulfillment, wrong costs, and a confused warehouse.

How to fix it

You need a single route with conditional logic, not two separate routes competing. Here's exactly what to change:

1. Remove the Dropship route from the product form. Keep only "Manufacture" as the active route. This prevents both routes from firing simultaneously.
2. Create a reordering rule on the product with minimum quantity = 0 and preferred route = Manufacture. When stock drops below minimum after a sale, Odoo will automatically create a manufacturing order to replenish.
3. For dropship scenarios, create a separate product variant that uses only the Dropship route. Your sales team selects this variant when the customer explicitly requests direct delivery from the supplier.
4. Link the operations together by setting procurement group propagation to "Fixed" on the manufacture route. This ensures the delivery order stays in "Waiting" status until the manufacturing order is completed.

I proposed the fix as a write action and you approved it:

Verified on your live database: confirming a sale now creates a single delivery in Waiting, the reordering rule raises the manufacturing order, and the delivery flips to Ready when it completes. One path, correct costs, no double fulfillment.

Environment Audit, 14 Custom Modules

I've scanned the full environment, every installed custom module, its dependencies, what standard Odoo behavior it overrides, and the risk level if you need to modify or remove it. Here's the complete picture.

Module Inventory

... and 9 more modules analyzed, full report available on request

Module Dependencies

The 2 high-risk modules sit at the top of the dependency chain:

• custom_sale_workflow → sale_margin_ext → report_templates
• stock_barcode_custom → mrp_quality_ext
• hr_expense_rules, standalone, no dependencies

You cannot uninstall or modify a module without first understanding everything downstream of it.

Risk Summary

• 2 high-risk modules, custom_sale_workflow and stock_barcode_custom heavily override core Odoo behavior. Any changes to these could break daily operations for the sales and warehouse teams. Understand them completely before touching anything.
• 4 medium-risk modules, extend standard features with custom fields and modified views. Functional but will need updates if the client upgrades Odoo versions.
• 8 low-risk modules, mostly report templates, small field additions, and UI tweaks. Safe to maintain as-is.