Migrate from BlueCamroo to Odoo CRM

BlueCamroo Organizations are the parent container for all sub-records and map directly to Odoo res.partner records with the is_company flag set to True. Organization name maps to partner name, and we preserve the BlueCamroo Organization ID as a custom field bc_organization_id__c for lookup resolution when importing child People records. Multi-address Organizations in BlueCamroo (billing vs shipping) map to separate res.partner addresses of type 'invoice' and 'delivery' linked to the same company partner record. We import Organizations first in every migration because all other record types reference them.

BlueCamroo People records map to Odoo res.partner with is_company = False, representing individual contacts. The BlueCamroo Organization ID on each Person record is resolved against the newly created res.partner IDs to set the parent_of field in Odoo, establishing the contact-company relationship. We export the Organization-ID-to-partner-ID mapping during the Organization phase and apply it during People import so that no Person lands without a parent company. Fields including email, phone, job title, department, and address components migrate to Odoo contact fields.

BlueCamroo Opportunities linked to Organizations map to Odoo crm.lead records with type = 'opportunity'. The BlueCamroo deal stage maps to Odoo's stage_id within the relevant CRM pipeline, and we create Odoo CRM pipeline stages matching the BlueCamroo pipeline structure before migration. Probability, expected close date, and amount (as float) migrate to crm.lead fields. The Organization link resolves to the Odoo partner_id via the ID mapping table created during the Organization phase.

BlueCamroo Cases migrate to Odoo helpdesk.ticket records linked to the customer res.partner via partner_id. BlueCamroo case status (Open, In Progress, Closed, Re-Opened) maps to Odoo ticket stage values, and the original Organization becomes the ticket's customer. Email-to-ticket routing configured in BlueCamroo via Workflow Rules does not migrate; we document the email alias and routing configuration during discovery for manual reconfiguration in Odoo's incoming email server settings. Case priority maps to ticket priority.

BlueCamroo Projects map to Odoo project.project records with the project manager and team inherited from the BlueCamroo project owner and assigned users. Project stages migrate as Odoo stage records within the project. BlueCamroo task dependencies become Odoo subtask or dependency links in project.task. Project budget totals migrate as monetary values for reference; Odoo does not have a native budget enforcement field at the project level without the Project Accounting module, so we note this gap in the deliverable documentation.

BlueCamroo Tasks inside Projects migrate to Odoo project.task records linked to the parent project.project via project_id. Standalone BlueCamroo CRM Tasks map to project.task records with no project_id and a priority flag. Assignee resolution uses the BlueCamroo owner email matched against the Odoo res.users table; unresolved assignees land in a reconciliation queue for the admin to provision. Subtasks and checklists in BlueCamroo become child project.task records in Odoo with the same parent_id linkage.

BlueCamroo time entries with billable/unbillable flags, hours, and linked project owner migrate to Odoo account.analytic.line records (used by both the Timesheet and Project apps). The employee_id on the timesheet line resolves from the BlueCamroo user email against the Odoo hr.employee table. Billable flag maps to a custom field or the Odoo Analytic Timesheet sheet structure. We preserve the original date, duration, and description. Non-project time entries (e.g., general CRM activity time) are imported as analytic lines without a project reference.

BlueCamroo Products and Services lists map to Odoo product.template records with type = 'consu' (consumable) or 'service' as appropriate. Price Books in BlueCamroo with per-account pricing tiers become Odoo product.pricelist records with pricelist items linked to the product.template. We create a base pricelist during migration and note that multi-account tiered pricing requires manual configuration of additional Odoo pricelists by the admin post-migration.

BlueCamroo invoices generated from project costs, stage percentages, or fixed dates migrate to Odoo account.move records of type 'out_invoice' (for customer invoices) with payment status preserved. Invoice line items resolve the product_id against migrated product.template records and the partner_id against the res.partner mapping. Open invoices migrate with state = 'draft' so the admin can review before posting; paid invoices migrate with state = 'posted' and reconciled payment records where available. Historical invoices that are fully paid require payment matching against the account.bank.statement.line to set state = 'paid'.

BlueCamroo Custom Forms (renamed from Extra Data Objects in version 8.3.10) hold custom sub-object data linked to accounts, contacts, projects, and cases. Each Custom Form requires configuration in Odoo via Settings > Technical > Fields: we pre-create the custom fields with appropriate Odoo field types (char, float, text, selection, many2one, etc.) on the target model (crm.lead, res.partner, project.project, project.task, or helpdesk.ticket) before any data import. Custom Form record data then imports via CSV or direct ORM insertion. We query both the Extra Data Object and Custom Forms API endpoints during discovery to ensure no custom data container is missed.

BlueCamroo's per-module subscription model assigns each user a role controlling extension access. When migrating to Odoo, we map BlueCamroo user roles to Odoo res.users records with the appropriate access rights configured in Settings > Users. BlueCamroo CRM-only users become Odoo CRM users; BlueCamroo Complete users become Odoo users with multi-app access. Note that Odoo permissions are controlled per app through the Odoo access rights interface, not a role-extension model like BlueCamroo's per-user per-module billing.

BlueCamroo Workflow Rules are configuration records, not data records, and have no export path via the BlueCamroo API or Reports. Every automation a customer has built — case routing, lead nurturing, project stage triggers, email notifications, assignment rules — must be manually recreated in Odoo Automations (or Odoo Studio server actions). We document every active Workflow Rule during discovery: trigger type, condition logic, action sequence, and which records it affects. The deliverable is a written rebuild guide mapped to Odoo's Automations interface. The customer or an Odoo partner rebuilds these post-migration.