Migrate from Dubsado to Zoho CRM

Dubsado Clients (contacts with a required email field) split into Zoho CRM Contacts and Accounts. Company name from Dubsado becomes the Account Name; the Client's name fields split into Contact First Name and Last Name. The Dubsado Client email, phone, address, and Internal Notes migrate to matching Zoho Contact fields. We use email as the deduplication key on insert. Client Custom Fields migrate to Zoho Custom Fields on Contact with type alignment (dropdown to picklist, text to text, checkbox to checkbox).

Dubsado Projects are the central container and do not map directly to a single Zoho CRM object. Active Projects with a monetary value and a client become Zoho CRM Deals attached to the mapped Account. Completed or archived Projects without active revenue are captured as Notes on the Account with Project Status, completion date, and description. We resolve the parent Client-to-Account lookup at migration time before inserting Deals. Project creation date and status history are preserved in Deal fields or Note body.

Dubsado Invoices (with ID, amount, status, due date, line items, and payment records) map to Zoho CRM Quotes for active billing relationships, preserving invoice number, amount, status, due date, and line items. Dubsado Payments and Dubsado Payments transaction IDs migrate as custom fields on the Quote record. For customers using Zoho Books for accounting, we deliver an invoice mapping spreadsheet to the Zoho Books migration scope; CRM Quotes do not carry a full accounting ledger entry in Zoho CRM alone.

Dubsado Contracts (status, related Client, and signature timestamps) migrate as Notes on the linked Account or Contact, capturing contract status, execution date, and expiry. The contract PDF content requires separate export from Dubsado as a file download and is uploaded to Zoho CRM as an Attachment linked via ContentDocumentLink to the Account. Signature data (name, timestamp, IP) is captured in the Note body. We flag any unsigned contracts as pending in the mapping notes.

Dubsado Proposals (a Premier-plan feature) map to Zoho CRM Quotes. Proposal status and linked Client and Project data migrate directly. The proposal content body requires a separate export from Dubsado's UI and is imported as a Note or as an Attachment on the Quote record. Proposals sent but not yet converted are flagged as open in Zoho Quote status.

Dubsado form submissions (field labels and values linked to Projects) migrate as Zoho CRM Leads. Each form submission becomes a Lead record with form field values mapped to Lead custom fields. Form field names align with Zoho custom field definitions during the mapping phase. We recommend rebuilding forms in Zoho Forms post-migration; the submission data migrates as Lead records but the form builder itself is not portable.

Dubsado Tasks (assignee, due date, completion status, linked Project) migrate to Zoho CRM Tasks with Subject, Status, Priority, and Due Date preserved. We store the parent Project reference as a custom field on the Task for audit. Assignee resolution matches Dubsado User email to Zoho CRM User email. Completed timestamp migrates as a custom Task field since Zoho Task does not natively store completion time separately from status.

Dubsado Time Entries (duration, date, linked Task, and billable flag) migrate to Zoho CRM as Notes on the linked Account with a structured text body capturing duration, date, Task reference, and billable status. For customers with significant time tracking needs, we recommend building a Zoho Projects custom module to hold time entries; we document the schema for that module during scoping and leave the data in structured Note format in the CRM scope.

Dubsado Custom Fields on Clients and Projects map to Zoho CRM custom fields on Contact and Deal. We export field definitions including type, label, and options from Dubsado and create equivalent Zoho custom fields with type alignment before migration begins. Dropdown options migrate as picklist values; multi-checkbox options migrate as multi-select picklist in Zoho. Field dependencies and conditional visibility rules are not portable and are documented for manual rebuild.

Dubsado canned email templates (body content and merge field syntax) migrate as Zoho CRM Email Templates. We export template subject and body as text, preserving merge field placeholders. Merge field mapping between Dubsado and Zoho syntax is validated per template during the sandbox migration phase; any broken merge tags are flagged for correction before production cutover.

Dubsado Client Portal access (per-Client flag and portal-specific customizations) migrates as a Note on the Account or Contact documenting portal status and any custom banner or permission settings. The Dubsado portal URL is captured as a custom text field. Zoho CRM does not have a native client portal equivalent; customers needing portal functionality typically deploy Zoho Customer Portal or Zoho Sites post-migration.

Dubsado Packages (reusable service bundles with name, description, pricing, and included items) migrate as Zoho CRM Products with Product Name, Unit Price, and Product Description. Package line items are captured as Notes on the Product record. Discount templates migrate as Price Book discounts applied at the Deal level in Zoho.