Migrate from Dubsado to Twenty CRM

Dubsado Clients map to Twenty CRM Person records. We extract First Name, Last Name, Email (required), Phone, Company name, Address, and Internal Notes. Dubsado's Client-level Custom Fields map to Twenty CRM Person custom fields. Email is the dedupe key during import. If the Dubsado Client has a distinct Company name separate from the individual, we create both a Person and a Company record and link them via the WorkRawRelation object in Twenty. Client Portal access status does not migrate; it is documented as a post-migration configuration item.

Dubsado Projects are the central container linking a Client to their service engagement. We map Projects to Twenty CRM Opportunities with Project Status translated to Opportunity Stage (Draft/In Progress maps to Negotiation, Completed maps to Closed Won or Closed Lost). Project creation date and description migrate to Opportunity fields. If a Dubsado Client has multiple active Projects, each becomes a separate Opportunity linked to the same Person. Project-level Custom Fields map to Opportunity custom fields. Note that Twenty does not have a native Project object; Project-specific deliverables and milestones require a custom object or task-based tracking.

Dubsado's configurable Project statuses (Active, Completed, Archived, On Hold, etc.) map to Twenty CRM Opportunity stage values. We configure stage labels in Twenty to match Dubsado's status language during migration setup. Closed Won and Closed Lost stages in Twenty capture Dubsado's Completed and Archived statuses with the appropriate close date.

Dubsado Contracts (with signature data, status, and timestamps) map to a custom Contract object we pre-create in Twenty CRM, or to Opportunity-level fields if the customer prefers a lighter schema. Contract template content (PDF body, field data) requires separate export and is attached to the custom Contract record as a file. Contract status (Sent, Signed, Declined, Expired) migrates as a custom picklist field. The actual e-signature document content does not migrate as searchable text; we attach the exported PDF and document the original signature timestamp.

Dubsado Invoices (ID, amount, status, due date, line items, payment records) map to a custom Invoice object we pre-create in Twenty CRM, or to Opportunity-level fields for simpler schemas. Invoice status (Paid, Unpaid, Partial, Overdue) migrates as a custom picklist. Recurring invoice schedules migrate as metadata on the custom Invoice object. Dubsado Payments transaction IDs are preserved for reconciliation. Note that Twenty has no native payment processing; invoices migrated are historical records only.

Dubsado Public Proposals (Premier-tier feature only) migrate as a custom Proposal object linked to the related Person and Opportunity. Proposal status (Draft, Sent, Viewed, Accepted, Declined) migrates as a custom picklist. The proposal content body (rich text with pricing tables) requires separate export and is stored as a text field or file attachment on the custom Proposal record. Proposals sent but not yet converted are flagged for manual follow-up post-migration.

Dubsado Form submissions (questionnaire responses linked to Projects) map to a custom FormSubmission object linked to the related Person. Field labels and values migrate as key-value pairs. Custom form field definitions from Dubsado's field builder map to field definitions on the custom FormSubmission object in Twenty. We capture form submission timestamp and source form name for attribution.

Dubsado Custom Fields on Clients and Projects are exported with type, label, and option definitions. We pre-create custom fields in Twenty CRM with type alignment: Dubsado text fields map to TEXT, dropdown options map to SELECT, multi-select maps to MULTI_SELECT, date fields map to DATE. Dropdown option values require manual review against Twenty's picklist constraints. Custom field values on existing records are migrated after the field schema is deployed.

Dubsado Tasks live within Projects and have assignees, due dates, and completion status. We export task records linked to their parent Project and map to Twenty CRM Tasks with the related Person or Opportunity (from the Project mapping) as the context record. Task status (Pending, Completed) maps directly. Full task history including completion timestamps is captured. Note that Twenty Tasks do not support sub-tasks natively; parent-child task hierarchies in Dubsado flatten to individual tasks with a custom parent reference field.

Dubsado Time Entries (duration, date, linked Task ID, billable flag) map to a custom TimeEntry object linked to the related Task and Person. Billable time linked to invoices is cross-referenced with the Invoice mapping for reconciliation. Time entries without a billable flag or invoice link migrate as historical records only. Non-billable time tracking has no native equivalent in Twenty CRM and requires the custom object approach.

Dubsado User accounts (name, email, role: Owner, Manager, Team Member) export with their role assignments. We match Dubsado users to Twenty CRM Users by email. Owner, Manager, and Team Member roles map to Twenty CRM role assignments post-migration. Note that Dubsado does not merge User and Contact data; team members who are also clients appear as both a User and a Client record and must be manually reconciled if deduplication is desired.

Dubsado canned email templates (body content, subject lines, merge field syntax) export as text. We store them in a custom EmailTemplate object in Twenty CRM. Merge field syntax varies by destination; field mappings require per-template validation against Twenty's token format. Templates are reference material for manual rebuild rather than importable assets.