Migrate from Berry crm to Odoo CRM

Berry CRM Contact records map to Odoo res.partner with type = 'contact'. The partner's name, email, phone, and address fields migrate directly. We detect the Berry CRM Contact-to-Company relationship and create it as a child Contact of the parent Partner in Odoo using the address subtype model. If Berry CRM stores multiple email addresses or phone types per contact, we capture them in Odoo partner contact information fields or custom fields as scoped during discovery.

Berry CRM Company records map to Odoo res.partner with type = 'company'. The company name becomes the partner name, domain or website is captured, and any associated addresses migrate as child contact records under the company partner. The Berry CRM Company-Contact linking table is resolved at migration time so that child contacts reference the correct parent_company partner id. Company-specific custom fields are recreated on the res.partner model before import.

Berry CRM Deals map to Odoo crm.lead records with type = 'opportunity'. Deal stage names map to Odoo CRM stage names (New, Qualified, Proposal, Won, Lost) which we configure during Odoo setup to match the source stage names exactly. Deal amount maps to Odoo planned_revenue, close date maps to date_deadline, and any deal description or notes map to crm.lead description. Deal-contact and deal-company associations resolve to Odoo's partner_id and partner_invoice_id and partner_shipping_id references.

Each distinct stage name in Berry CRM Deals becomes an Odoo crm.stage record within the default pipeline. Stage sequence order is preserved. We configure probability percentages per stage that match the source data distribution where available. The Odoo stage IDs are resolved before Deals import so that stage references are valid on insert.

Berry CRM Sales Quotes map to Odoo sale.order records in draft state. Quote line items map to sale.order.line with product, quantity, unit price, and discount. Quote totals and tax computation are handled by Odoo's sale.order compute method after line import. Quote-to-deal associations are preserved by linking the sale.order to the corresponding crm.lead via the origin reference field if Odoo's Sale module is installed. If only the CRM module is present, we link by partner and note the origin deal id in a custom field.

Berry CRM Products map to Odoo product.product records. Product name, description, default_code (SKU), list_price, and standard_price migrate directly. We set the product type (storable, consumable, service) based on the product's usage in Berry CRM quotes and invoices. Inactive or archived products in Berry CRM are migrated as inactive records in Odoo unless the customer specifies otherwise during scoping.

Berry CRM Price Books map to Odoo product.pricelist records. Each price list entry in Berry CRM becomes a product.pricelist.item linked to the corresponding pricelist. The Price Book-to-Product relationship is resolved at migration time using product SKU as the dedupe key. Pricelist currency is inferred from the Price Book name or set to a default; the customer confirms currency during scoping.

Berry CRM Projects map to Odoo project.project records. Project name, description, status (active/closed), and start date migrate directly. We link project to the corresponding Berry CRM company or contact via a custom field (x_berry_company_id) because Odoo Project's native customer field (partner_id) is optional. Project-task associations are preserved through the project-task linking table so that tasks migrate with their parent project reference intact.

Berry CRM Tasks map to Odoo project.task records. Task title, description, due date, assignee (mapped to Odoo user by email match), and completion status (stage_id in Odoo) migrate directly. Tasks that are not linked to a project in Berry CRM are imported into a default migration project or held in a reconciliation queue for the customer to assign. The task's related contact or company is stored in a custom field x_berry_contact_id for cross-reference.

Berry CRM Invoices map to Odoo account.move records with move_type in ('out_invoice', 'out_refund'). Invoice line items map to move_line records, totals and payment status migrate, and invoice-to-contact associations resolve to res.partner. This mapping requires the Odoo Accounting module to be installed and configured; we verify module availability during scoping. If Accounting is not in scope, we flag Invoice migration as deferred and deliver invoice data in a structured CSV for manual import or future Accounting module activation.

Berry CRM custom fields are detected during the discovery export phase by comparing the actual exported data against the inferred base schema. Each detected custom field is analyzed for type (text, number, date, picklist, boolean) and then created as an Odoo custom field via Settings > Technical > Database Structure > Models in the Community edition, or via Odoo Studio in Enterprise. We create the mapping rule before importing the parent object and apply the value during the record insert. Custom field metadata (name, type, object) is documented in the mapping inventory delivered to the customer.

Berry CRM Owner references on Contacts, Companies, Deals, and Tasks are resolved by email match against the Odoo destination res.users table. Owners without a matching Odoo user are held in a reconciliation queue and the customer provisions the corresponding users before record import resumes. Inactive or archived owners in Berry CRM are flagged for the customer's decision (provision as inactive Odoo user or reassign records to an active user).