Migrate from Dubsado to Microsoft Dynamics 365 Sales

Dubsado Clients with a Company name field map to a Dynamics 365 Account as the organizational record, with a primary Contact record created from the Client. Clients without a Company name map to a Contact without an Account (sole proprietor pattern). We preserve First Name, Last Name, Email (required in Dubsado), Phone, Address, Internal Notes, and Custom Fields. The split logic runs as the first transform so that Account is created before the Contact, satisfying the parent Lookup at insert time.

Each Dubsado Project becomes a Dynamics 365 Opportunity. Project name maps to Opportunity name. Project status (Active, Completed, Archived) maps to Opportunity stage: Active maps to the customer's defined open stage, Completed maps to Closed Won, and Archived maps to Closed Lost or Archived per the customer's stage configuration. Project creation date migrates to Opportunity CreatedOn for historical ordering. Projects with no linked Client become Opportunities without an Account (anonymous pipeline), flagged for manual Account assignment post-migration.

Dubsado Tasks live within Projects and map to Dynamics 365 Tasks linked via WhatId to the parent Opportunity. Task assignees resolve by email match to the provisioned Dynamics 365 User. Due dates, completion status, and completion timestamps migrate directly. We preserve full task history including completion timestamps against the original Project-level task list.

Dubsado Invoices migrate as structured records: Invoice ID, amount, status (paid/unpaid/partial), due date, line items, and payment records transfer to a custom Invoice entity or to notes on the parent Opportunity. Dubsado Payments transaction IDs are preserved in a custom field for audit. Note that Microsoft Dynamics 365 Sales does not include native invoicing — the invoice data is stored as a custom entity or linked record and the customer's admin configures reporting from that structure.

Dubsado Contract records (status, related Client, signature timestamps) migrate as Notes attached to the corresponding Account or Opportunity. The actual contract PDF content requires separate export from Dubsado and upload as a Dynamics 365 SharePoint document or Notes attachment. Signature timestamps and contract status are preserved in custom fields on the Note record.

Dubsado Custom Fields on Clients and Projects map to Dynamics 365 custom fields on Contact, Account, and Opportunity. We export field definitions (type, label, options) and align value types with Dynamics field types: Dubsado text fields map to Single Line of Text, Dubsado dropdowns map to Option Sets, Dubsado date fields map to Date fields. Multi-select Dubsado fields map to Dynamics Multi-Select Option Sets.

Dubsado form submissions with questionnaire responses and field labels map to Dynamics 365 Lead records (for pre-contact leads) or to Notes on the related Contact or Account. Form field names align with Dubsado's Custom Field definitions and must be validated against the destination custom field set. Form submissions without a linked Contact become Leads; those with a linked Contact become Notes on the Contact record.

Dubsado User accounts (Owner, Manager, Team Member roles) map to Dynamics 365 Users resolved by email match. Active Users with email matches migrate as active Dynamics Users; inactive Dubsado users migrate as inactive Dynamics Users for historical assignment. Users without an email are flagged for admin review. Role mapping (Owner, Manager, Team Member) is preserved in a custom field for reference since Dynamics 365 security roles operate differently.