Migrate from Dubsado to Pipedrive

Dubsado Clients map to Pipedrive People, with the Client's company name optionally mapped to a Pipedrive Organization record. We extract First Name, Last Name, Email (required), Phone, Company, Address, and Internal Notes. The Dubsado email address is the primary dedupe key during import. Any Dubsado Client Custom Fields (dropdown, text, date, checkbox) migrate as Pipedrive Custom Fields on Person, using field-type matching from Advanced tier or higher.

Dubsado Projects map to Pipedrive Deals. The Project's name becomes the Deal title, and the linked Dubsado Client maps to the Deal's linked Person. Project creation date migrates as a custom Deal field. Project status (Active, Completed, Archived) requires a mapping decision: we recommend Active and In-Progress Projects map to open Deals with appropriate Stage, while Completed and Archived Projects map to Won or Lost Deals with a custom status flag to preserve historical context.

Dubsado Project statuses do not have a direct Pipedrive equivalent, so we configure one or more Pipedrive Pipelines and Stages to receive them. For migrations with a single project workflow (e.g., Active / Completed only), a single Pipeline with two Stages is sufficient. For Dubsado accounts with custom status lists, we create a Pipedrive Pipeline per logical business workflow and map each Dubsado status to a Stage with a custom field dubsado_original_status__c preserved for audit.

Dubsado Invoices map to Deal-level custom fields because Pipedrive has no native invoicing object. We extract Invoice ID, Amount, Status (paid/unpaid/partial/overdue), Due Date, and the line item summary as a text custom field. Dubsado Payments transaction IDs from Dubsado Payments (Stripe-powered) are preserved in a custom field for reconciliation. Customers requiring full invoice history in Pipedrive integrate with FreshBooks, QuickBooks, or Pipedrive's Proposals tool post-migration.

Dubsado Contract records store status, related Client, signature timestamps, and the contract PDF content. We export contract status and signature data and attach them as a Note on the related Pipedrive Deal (or Person if no Deal exists). The actual PDF must be exported separately from Dubsado and reattached in Pipedrive. Pipedrive has no native e-signature feature; teams requiring contract execution migrate to DocuSign or PandaDoc as a post-migration step.

Dubsado Tasks live within Projects and have assignees, due dates, completion status, and full completion timestamps. We map these to Pipedrive Activities (Task type). Task status in Dubsado (complete/incomplete) maps to Pipedrive Activity status (done/open). Tasks linked to a Dubsado Project inherit the migration's Deal link so the Activity associates to the correct Pipedrive Deal.

Dubsado Custom Fields on Clients migrate to Pipedrive Custom Fields on Person objects. Dropdown fields in Dubsado map to Pipedrive SET-type fields; date fields map to date fields; checkbox fields map to boolean fields. We pre-create the destination Custom Fields in Pipedrive during schema configuration, matching the field label and type exactly. Value mapping is validated against Pipedrive's field-type constraints before import.

Dubsado Custom Fields on Projects migrate to Pipedrive Custom Fields on Deal objects using the same field-type matching approach as Client Custom Fields. Project-level custom data that tracks budget, deliverables, or project type becomes deal-level metadata in Pipedrive. This is one of the most common areas for mapping revision during sandbox testing.

Dubsado Lead Capture Form submissions (questionnaire responses linked to a Project) can be treated as Pipedrive Leads if the customer uses Pipedrive's Lead inbox. We export form submission field labels and values, map them to Pipedrive Custom Fields on Lead, and link the Lead to the corresponding Deal. Form response data in Dubsado that predates any active Project may not have a Pipedrive home; we flag these records during scoping and the customer decides whether to import as Leads or leave them behind.

Dubsado Users (Owner, Manager, Team Member roles) map to Pipedrive Users by email match. Dubsado role assignments (Owner, Manager, Team Member) have no direct Pipedrive equivalent, so we document the original role and map the closest Pipedrive role (Admin for Owner, Member for Manager and Team Member). Users without a matching Pipedrive account go to a reconciliation queue for the customer's admin to provision before migration proceeds.

Dubsado Proposals are a Premier-tier feature and contain custom content, line items, and proposal-specific data. We export proposal status, linked Client/Project, and a content export where available. The proposal body (rich text with pricing tables) cannot be structurally imported into Pipedrive; we export it as a text blob and attach it as a Note on the related Deal or Person. Pipedrive's native Proposals tool (Advanced plan) can be rebuilt manually using the exported content as reference.