Migrate from Accelo to Odoo CRM

Accelo Companies map to Odoo res.partner records with partner_type set to 'company' to activate the contacts-within-company hierarchy. The company name becomes partner_name, address fields map to street, city, state, country, and zip, and industry maps to an Odoo custom industry selection field we create during schema setup.

Accelo Contacts map to Odoo res.partner with partner_type set to 'person'. Contact-to-company linkage via the parent_id field maintains the company-contact hierarchy. Email, phone, mobile, title, and custom fields migrate directly. We preserve the contact's Accelo owner assignment in a custom field accelo_owner_id for staff assignment reconciliation.

Accelo Deals (Sales Pipeline) map to Odoo CRM crm.lead records classified as Opportunities. Deal name becomes the lead name, deal value maps to expected_revenue, and the pipeline stage maps to Odoo's stage_id with a customer-approved stage matrix created during scoping. Owner assignment resolves via the staff mapping.

Accelo Jobs are the core structural challenge of this migration. Each Job becomes an Odoo project.project record with phases mapped to task sections or sub-projects depending on the Job's phase depth. The Job's contract value maps to the project's allowed sale orders or contract module reference. We flag Jobs that have an active Retainer association as these require a separate Odoo Subscription or contract record alongside the Project.

Accelo Tasks map to Odoo project.task records linked to the parent project.project from the Job mapping. Task assignees map to Odoo project.user_ids. Due dates, checklists, and custom fields migrate; checklist items become child tasks in Odoo. Note that Accelo custom fields on Tasks are not exposed via the public API — we flag these for Odoo custom field creation post-migration.

Accelo time entries map to Odoo account.analytic.line (analytic accounting lines) linked to the Project from the Job mapping. Billable flag maps to the line's unit_amount and product mapping. Billable rate from Accelo's staff billing rate metadata migrates as a custom field or maps to the timesheet product unit price in Odoo's Timesheet app. Large time entry sets require pagination through Accelo's API because no bulk export exists.

Accelo Staff records map to Odoo hr.employee. We map staff email to employee work email, staff name to employee name, and department assignment to hr.department in Odoo. Staff role (Manager, Team Member, etc.) becomes an Odoo job_id reference. Owner-to-Staff mapping resolves at migration time for record assignment consistency.

Accelo Leads export via the Sales API and map directly to Odoo crm.lead records. Lead status maps to Odoo's stage_id, and source information migrates to the lead's source_id. Custom fields on Leads are preserved via Odoo's custom field system. We differentiate Leads from Deals during scoping based on the customer's Accelo pipeline configuration.

Accelo Tickets map to Odoo Helpdesk ticket records if the customer activates the Odoo Helpdesk app. Ticket subject maps to name, description to description, priority to priority, and status to stage_id. Ticket assignee maps to user_id in Odoo Helpdesk. If Odoo Helpdesk is not activated, tickets map to crm.lead with a custom ticket-type tag.

Accelo Retainers are compound objects that split into Odoo Subscription records (contract terms, prepaid balance, start/end dates) and associated Invoice records (billing activity). The Retainer prepaid balance migrates to the subscription's recurring_total. We document the Retainer-to-subscription mapping and flag any financial references to retired chart-of-accounts entries for the customer's accounting team to reconcile.

Accelo Invoice records map to Odoo account.move records of type 'out_invoice'. Line items migrate as invoice_line_ids with product, quantity, and price unit preserved. Invoice status (draft, sent, paid) maps to Odoo's state field. Historical invoice records may reference retired financial data — we flag these for the customer's accounting team and do not alter the source data.

Accelo file attachments on Jobs, Tasks, and Tickets export via /attachments endpoints and migrate as Odoo ir.attachment records linked via res_model and res_id to the target object (project.project, project.task, or helpdesk.ticket). We download files individually and re-upload to Odoo's document storage with the original filename preserved. Large attachment sets increase migration time proportionally.

Accelo ticket comment threads (conversations) map to Odoo mail.message records on the helpdesk.ticket. Each message preserves body text, author (mapped to res.partner), and create_date for thread ordering. Comments on Jobs and Tasks use a different Accelo endpoint — these migrate as project.task messages or note records depending on the customer's Odoo configuration.

Accelo custom fields on Companies and Contacts migrate to Odoo custom ir.model.fields created via Odoo Studio before data migration. We create text, selection, date, and integer field types matching the Accelo field type. Choice-based fields become Odoo selection fields with matching option values. Field-level security in Odoo is set to editable for the relevant user groups during migration.

Accelo Categories on Companies, Contacts, and Deals map to Odoo CRM tags via crm.tag records. Each unique Accelo category value becomes a tag name. We create the tag records before migration and link them to migrated records via the tag_ids many2many field on crm.lead.