Migrate from Dubsado to Salesforce Sales Cloud

Dubsado Clients map to either Salesforce Lead or Contact depending on whether a related Project exists in Dubsado. Clients with at least one Active or Completed Project map to Salesforce Contact linked to an Account (the Account is created from the Client's Company field or a synthesized account name if Company is empty). Clients with no Projects map to Salesforce Lead. Email, Phone, Company, Address, and Internal Notes migrate to the corresponding Salesforce fields. Custom Fields on Client migrate to typed Salesforce fields with values preserved as text.

Dubsado Clients with a populated Company name map to a Salesforce Account. The Account Name field receives the Dubsado Company value; if Company is empty, we synthesize an Account Name from FirstName LastName and flag it for admin review. Account is created before any Contact import so that AccountId is available at Contact insert time.

Dubsado Projects map to Salesforce Opportunity. The Dubsado Project status (Active, Completed, Archived) maps to a Salesforce StageName via a status-mapping matrix defined during scoping. We create one Opportunity per Project and link it to the Account derived from the parent Client. Project creation date and last-modified date migrate as Opportunity CreatedDate and LastModifiedDate for historical accuracy.

Each Dubsado Project status becomes a Salesforce Opportunity Stage with an associated probability percentage defined during scoping. We configure a single Sales Process (or one per brand if the customer uses multiple Dubsado brands) to whitelist the migrated stage values. Archived Projects map to Closed Lost or a custom Stage value chosen by the customer.

Salesforce has no native invoice object. Dubsado Invoice data—Invoice ID, amount, status, due date, line items, and payment records—migrates as typed custom fields on the Opportunity record linked to that Project. We create custom fields such as dubsado_invoice_id__c, dubsado_invoice_amount__c, dubsado_invoice_status__c, dubsado_due_date__c, and a long-text area for dubsado_line_items__c containing the original invoice line-item JSON for admin reference. Dubsado Payments transaction IDs are preserved in dubsado_payment_transaction_id__c.

Dubsado Contract records (status, related Client, signature timestamps) migrate as custom fields on the Account or Opportunity. The actual contract PDF content migrates as a ContentDocument attached via ContentDocumentLink to the Account record, preserving the signed document for audit. Unsigned contract templates are documented in the migration checklist with a recommendation to regenerate from Salesforce native tools or DocuSign.

Public Proposals are a Premier-tier feature in Dubsado and cannot be exported as structured data. We migrate proposal status and the linked Client and Project as Opportunity-level custom fields. Proposal content body is not migratable in structured form; we provide a document listing every active proposal with its status, linked client, and date so the customer's admin can reproduce or recreate proposals in Salesforce or a connected quoting tool. Proposals sent but not yet converted are flagged as open items.

Dubsado Custom Fields on Client and Project map to typed Salesforce custom fields. Short-answer text fields map to Text, email to Email, phone to Phone, date to Date, checkbox to Checkbox, and dropdown to Picklist or Text. Options lists in Dubsado dropdowns map to Salesforce Picklist values. We pre-create the destination schema in a Sandbox before migration and validate field-type compatibility with existing Salesforce validation rules. Custom field labels are preserved as Field Label; API names receive the dubsado_ prefix to avoid naming collisions.

Dubsado Tasks live within Projects and have assignees, due dates, completion status, and completion timestamps. We export Tasks linked to their parent Project and create Salesforce Tasks with Subject, Status, Priority, ActivityDate, and the Dubsado completion timestamp in a custom field dubsado_completed_at__c. Task assignment migrates by resolving the Dubsado assignee email to a Salesforce User record.

Dubsado Time Entries tied to Projects and Tasks migrate to Salesforce Event records. Duration in minutes maps to Event.DurationInMinutes; the original Dubsado Task ID is preserved in a custom field dubsado_task_id__c for audit. Billable time linked to invoices is cross-referenced with the migrated Invoice custom fields on the Opportunity. Time entries without a parent Task are linked directly to the Opportunity.

Dubsado Lead Capture Form submissions store field labels and values linked to a Project. We export field labels, values, and submission timestamp. For straightforward form structures, field-value pairs migrate as Opportunity-level custom fields (one field per form question). For complex multi-page forms, we recommend creating a Dubsado_Form_Submission__c custom object with Name, Opportunity__c (lookup), Form_Name__c, Submission_Date__c, and a long-text dubsado_responses__c field containing the full submission JSON. The customer chooses the approach during scoping.

Dubsado Packages are reusable service bundles appearing on Proposals and Invoices. We export package definitions including name, description, and included items. If packages represent billable service products, they map to Salesforce Product2 records with Standard Pricebook entries. If they represent pricing templates without separate product tracking, they migrate as Opportunity-level text fields capturing the package name and pricing for historical record.

Dubsado canned email templates and merge field syntax migrate as Salesforce EmailTemplate records with the template body as plain text. Merge field mappings vary from Dubsado's syntax (e.g., {{client.firstName}}) to Salesforce's ({!Contact.FirstName}); we transform merge field tokens during migration and flag any unresolvable tokens for admin review. Subject lines migrate as the EmailTemplate Subject field.

Dubsado Client Portal access status (active/inactive) and portal-specific customizations migrate as custom fields on the Account record: dubsado_portal_access__c (Checkbox) and dubsado_portal_url__c (URL). The portal URL must be reconstructed in Salesforce Experience Cloud (Community) if the customer wants to continue offering a branded client portal; we document the portal configuration requirements as part of the post-migration handoff.

Dubsado User accounts (Owner, Manager, Team Member roles) are extracted and matched by email to Salesforce User records. Dubsado Owners without a matching Salesforce User go to a reconciliation queue for admin provisioning. We do not create Salesforce Users; we only map existing ones. Role assignments are noted for the customer's admin to assign Salesforce Profiles and Permission Sets post-migration.