Migrate from Dubsado to HubSpot

Dubsado clients map 1:1 to HubSpot contacts. First name, last name, email, phone, and address fields transfer directly with no transformation required. Dubsado's 'client' is a single flat record; HubSpot contacts are the primary record type for all person-based data and serve as the foundation for HubSpot's contact-centric data model. All contact-level information in Dubsado lands in HubSpot as native contact properties.

Dubsado stores a single company name per client contact. That company name becomes a HubSpot Company record, and the Dubsado client is associated to it via a primary company link. Multiple Dubsado clients sharing the same company name are linked to the same HubSpot Company.

Dubsado projects are the core work record — they contain the client, status, pipeline stage, amount, and due date. Each project becomes a HubSpot deal. The Dubsado project status (Active, Halted, Completed) maps to a HubSpot deal stage; your team chooses which HubSpot pipeline receives each project type.

Dubsado project status values (e.g., Lead, In Progress, Pending Review, Completed, Invoiced) map to HubSpot deal stages per pipeline. Each distinct Dubsado project status becomes a HubSpot stage in the selected pipeline. Stage probability and forecast category are applied based on HubSpot's defaults or your custom stage configuration.

Dubsado custom fields on clients (dropdown, text, number, date types) are replicated as HubSpot custom contact properties. Property type is matched — a Dubsado date field becomes a HubSpot date property; a Dubsado dropdown becomes a HubSpot option-set property. Property groups in HubSpot are used to match Dubsado's field groupings.

Dubsado custom fields on projects migrate as HubSpot custom deal properties. If a Dubsado project custom field captures information relevant to the deal record (e.g., project type, deliverable count), it lands as a custom deal property. Fields that are purely administrative in Dubsado can be flagged to drop.

Dubsado leads captured via lead capture forms have no lifecycle stage — they represent a project-not-yet-started state with no sales progression tracking. These records migrate as HubSpot contacts with lifecycle_stage set to 'subscriber' by default. Original form submission date is preserved as a custom datetime property for attribution continuity, allowing your team to maintain source tracking data in HubSpot.

Dubsado invoice records contain amount, status (paid/unpaid/overdue), and payment method. The invoice PDF is exported as a file and attached to the corresponding HubSpot deal. Invoice payment status migrates as a custom deal property; payment history requires a post-migration Stripe or QuickBooks integration to reproduce Dubsado's payment automation.

Dubsado contract PDFs migrate as files attached to the associated HubSpot contact or deal. Contract status (sent, viewed, signed) and signature date are preserved as custom properties on the contact. Dubsado's contract template structure does not migrate — rebuild using HubSpot Documents, DocuSign, or PandaDoc.

Dubsado team members map to HubSpot users by email match. Dubsado's permission model (owner, team member, view-only) does not have a direct HubSpot equivalent — HubSpot roles and permissions are configured post-migration. Project assignment in Dubsado becomes deal owner assignment in HubSpot via email lookup.

Dubsado tasks assigned to a client or project migrate as HubSpot tasks linked to the corresponding contact or deal. Task status, due date, and assignee are preserved. Dubsado's task board view does not have a HubSpot equivalent — task lists in HubSpot are per-record rather than board-based.

Dubsado time tracking entries (hours logged against a project) are aggregated and stored as a custom number property on the HubSpot deal. Dubsado's per-entry time log does not map to a native HubSpot object — a project management integration (e.g., Toggl, Harvest) is needed for granular time tracking post-migration.

Dubsado canned email templates are text-based templates attached to workflows or manually sent. They do not migrate — FlitStack AI exports them as text files for reference, but they must be recreated as HubSpot Sales Email templates or imported into HubSpot Sequences manually. This is a manual rebuild item disclosed upfront.