Migrate from Dubsado to Odoo CRM

Dubsado Clients map to Odoo res.partner records. We apply a split rule during migration: Clients with a Company name field populated become res.partner records with is_company=True (the Company). Individual contacts at that company become separate res.partner records with parent_id pointing to the Company partner. Clients without a company name become individual res.partner contacts with is_company=False. Dubsado Client custom fields map to res.partner custom fields (ir.model.fields with track_visibility). Email is the dedupe key during import.

Dubsado Projects have no direct Odoo CRM equivalent because Odoo separates sales pipeline (crm.lead / crm.lead) from project delivery (project.project). We apply a split rule during scoping based on project status and intent: Projects with status Active and intent to sell become Odoo crm.lead records (with stage set to a Dubsado-mapped pipeline stage). Projects with status Completed or intent to deliver become project.project records with the client as project.partner_id. Customers choose the split strategy during discovery. Project creation date and status history are preserved in custom fields on both record types.

For Dubsado Projects that map to crm.lead, we create an Odoo Opportunity record. The Dubsado project name becomes the Opportunity name, the linked Client maps to res.partner via the client mapping, and project total value maps to crm.lead.planned_revenue. We configure Odoo pipeline stages during migration setup to match Dubsado project statuses (e.g., Inquiry, Proposal Sent, Contract Signed, Active, Completed) as crm.stage records with sequence and is_won/is_lost flags.

Dubsado Invoices map to Odoo account.move records with move_type='out_invoice' for standard invoices and move_type='out_refund' for credits. We preserve Invoice ID, amount, status (paid/unpaid/partial/void), due date, line items (product, quantity, unit price, tax), and Dubsado Payments transaction IDs. If Odoo Accounting is in scope, we set the journal to the customer's default sale journal. Recurring invoice schedules migrate as recurring.template records linked to sale.subscription if the customer enables the Odoo Subscription module.

Dubsado Contracts store PDF documents with signature data (signing timestamp, signer name). We export the contract PDF as an ir.attachment linked to the related res.partner and/or crm.lead record. Contract status (sent, signed, expired), related Client, and signature timestamps migrate to custom fields on the linked partner or lead. The actual contract PDF body content is preserved as an attachment; we do not extract individual field data from the PDF. Contract templates do not migrate as reusable templates in Odoo; the customer's admin recreates templates in Odoo Studio or via a document template app.

Dubsado Public Proposals (Premier-plan only) map to Odoo sale.order records with state='draft'. Proposal status (draft, sent, viewed, signed) maps to Odoo sale.order state and a custom field proposal_status__c. Proposal line items map to sale.order.line records with product, description, quantity, and price. Note that Odoo requires sale_timesheet or sale_stock modules to be installed for time-and-materials or subscription proposals; we confirm the relevant Odoo apps during discovery.

Dubsado Lead Capture Form submissions map to crm.lead records with the lead_source set to the form name and the form submission data stored in a custom field (lead_form_data__c) as JSON. We export form field labels and values. Odoo does not have a native form builder equivalent to Dubsado's Lead Capture Forms; the customer's admin rebuilds forms using Odoo Website builder (if installed) or a third-party form app from the Odoo Apps store. Form templates do not migrate as reusable forms.

Dubsado custom fields on Clients map to custom ir.model.fields on res.partner. Dubsado custom fields on Projects map to custom ir.model.fields on crm.lead or project.project depending on the project split decision. We preserve field type (short answer maps to char, date maps to date, dropdown maps to selection or many2one depending on whether the options represent a related record type). Field options are preserved as selection values or related model records. We create the custom fields in Odoo via XML data migration before importing data so that field data is written into typed columns rather than unstructured notes.

Dubsado Tasks map to project.task records. We link each task to its parent Dubsado Project via project_id, set task.stage_id to the Odoo stage matching the Dubsado task status, and preserve assignee (user_ids), due date, creation date, and completion date. Dubsado task notes migrate as project.task.description (plain text). Task subtasks do not have a native Odoo equivalent; we flatten subtask relationships into a parent_task_id link where available or into a project.task custom notes field.

Dubsado Time Entries map to account.analytic.line records (used by Odoo Project for time tracking). We preserve duration (unit_amount), date, linked task_id (via project.task), and billable flag. Billable time entries linked to Dubsado Invoices are cross-referenced with account.move line records during invoice migration. If the customer does not install Odoo Project or Timesheet apps, time entry data migrates as a project.task custom field for reference only.

Dubsado Client Portal access status and per-client portal settings migrate as res.users records with share=True (portal user) linked to the res.partner client record. Portal-specific customizations (banner image, access permissions) are documented as a portal.config audit record because Odoo's portal access is configured via website.portal and access.control.list models rather than per-partner flags. Portal URL mapping is documented in the migration checklist. Note: Odoo portal access requires the website module and may require additional configuration beyond a basic CRM setup.

Dubsado Team Members map to Odoo res.users records. Owner maps to res.users with admin=True; Manager maps to res.users with groups_id including sales_manager; Team Member maps to res.users with sales_user. Dubsado does not have a granular permission model, so the mapping is a best-effort translation. We export active users and their role assignments. If a Dubsado user does not have an Odoo login provisioned, they go to a reconciliation queue for the customer's admin to provision before production migration.

Dubsado Canned Email Templates export as mail.template records in Odoo. We preserve template name, subject, and body content (plain text or HTML). Dubsado merge field syntax (e.g., [Client Name]) is documented with a mapping table to Odoo Jinja2 field syntax (e.g., {{ object.partner_id.name }}). The customer's admin validates merge field mappings per template after migration. Template categorization does not migrate; we create a single folder in Odoo for migrated templates with a reference to the original Dubsado template name.

Dubsado Packages (reusable service bundles) map to Odoo product.product records with type='service' and a product.template containing the package description. Package line items map as BOM lines on the product.template if the Odoo Manufacturing or Quoting apps are installed. Otherwise, package details are stored in a product description field and the customer's admin reconstructs package templates in Odoo Studio. Discount templates map to sale.order.line discount fields on the product or quotation line.