Migrate from Dubsado to Freshsales

Dubsado Clients map directly to Freshsales Contacts. First Name, Last Name, Email, Phone, Company, Address, and Internal Notes migrate as standard Contact fields. Dubsado Custom Fields on Clients map to Freshsales custom contact fields; dropdown options from Dubsado map to Freshsales picklist values. Email is the primary dedupe key. The migration requires the Contact to be created first since most other Dubsado objects (Projects, Invoices, Contracts) link back to the Client as a parent.

Dubsado Projects are the central data container with no direct Freshsales equivalent. Active Dubsado Projects with a status of Active or In Progress map to Freshsales Deals with the project title as Deal Name and the project status preserved in a custom field project_status__c. Completed and Archived Projects map to historical Deal records with a Closed status. If the customer needs to preserve full project context, we create a custom Project object in Freshsales with a lookup to Contact. Dubsado project creation dates and last-modified timestamps migrate as custom date fields for historical reference.

Dubsado Clients without a separate Company field link their company name to the Client record itself. If a Dubsado Client has a populated Company field, we create a Freshsales Account for that company and link the Contact to it via the Account Lookup. Multiple Dubsado Clients that share the same Company name are consolidated into a single Freshsales Account with multiple Contacts. This is a common scenario for agencies managing multiple contacts within the same client organization.

Dubsado Invoices have no direct Freshsales equivalent. We create a custom Invoice object in Freshsales with fields for Invoice ID, Amount, Status (paid/unpaid/partial), Due Date, and line items (via a custom Line Item child object or a multi-line text field). The Invoice links to the parent Contact via a Lookup relationship. Payment records and Dubsado Payments transaction IDs are preserved in a custom text field. Recurring invoice schedules migrate as metadata notes. Note that Freshsales does not process payments natively; customers should plan for a Stripe or FreshBooks integration post-migration for ongoing invoicing.

Dubsado Contracts store templates and executed agreements with signature data and timestamps. We create a custom Contract object in Freshsales with fields for Contract ID, Status (draft/sent/signed/expired), Related Contact, Signature Date, and a link to the contract PDF stored as a file attachment. The actual contract PDF migrates as a ContentDocument attached to the Contract record. Note that Freshsales does not have native e-signature; customers using Dubsado's built-in signature feature should plan for a DocuSign or HelloSign integration in Freshsales.

Public Proposals are a Premier-tier feature in Dubsado. Proposal status and linked Client/Project data migrate as a Freshsales Note with a custom note type field set to Proposal. The proposal content body requires separate export from Dubsado (a PDF or HTML export per proposal) and attaches to the Note as a file. Proposals sent but not yet converted migrate as draft notes for the customer's sales team to follow up on manually.

Dubsado Custom Fields on Clients and Projects migrate as Freshsales custom fields. We extract the field type from Dubsado (text, number, date, dropdown, checkbox) and map to the equivalent Freshsales field type. Dropdown options require validation against Freshsales picklist limits. Dubsado's custom mapped fields use smart field syntax ({{client.name}}) which does not transfer; these are documented as merge field reference notes for the customer's admin to rebuild in Freshsales templates.

Dubsado Tasks within Projects migrate to Freshsales Tasks linked to the parent Contact or Deal. Task assignees, due dates, completion status, and creation timestamps migrate directly. Full task history including completion timestamps is preserved. Note that Freshsales Tasks do not have the same project hierarchy context as Dubsado; we document the original Dubsado Project ID in a custom field task_source_project__c for audit purposes.

Dubsado Workflows cannot be exported via any native tool or documented API endpoint. This is not a technical limitation we can work around; the automation data does not exist in an exportable format. We do not migrate Workflows. We provide a Workflow Audit Template that maps every trigger, condition, and action sequence for the customer's admin to rebuild in Freshsales' workflow builder. Customers on Premier tier should expect to spend 1-3 days documenting their workflows before migration begins.

Dubsado User accounts (Owner, Manager, Team Member roles) map to Freshsales User records by email match. The Dubsado role maps to a Freshsales custom role field since Freshsales roles are defined per workspace. Users without a matching Freshsales User go to a reconciliation queue for the customer's admin to provision. Active and inactive status migrates directly.