Migrate from Dubsado to Nutshell

Dubsado Clients map to Nutshell Contacts with First Name, Last Name, Email, Phone, Company, Address, and Internal Notes preserved. Email is required in Dubsado and maps directly to Contact.Email. Any Dubsado Client flagged as a business entity with multiple contacts becomes a Nutshell Account with a primary Contact, and secondary contacts are created as additional Contact records linked to that Account. Custom Field values on Clients migrate to Nutshell Custom Fields on Contact.

Dubsado Projects have no direct Nutshell equivalent. During scoping we determine the mapping strategy: Projects with tracked revenue or recurring billing become Nutshell Deals in the Pipeline, with project status mapped to Pipeline stage, project value mapped to Deal value, and a reference Note on the Contact. Projects that are informational or service-oriented without a formal sale become Notes on the Contact record, with project status, creation date, and related tasks documented in the Note body. The customer chooses strategy per-project-type during discovery.

Dubsado Invoices (ID, amount, status, due date, line items, payment records, recurring schedules) migrate as Nutshell Notes on the Contact record with a Document attachment for the PDF. Invoice status (paid, unpaid, partial) and Dubsado Payments transaction IDs are stored as Note body metadata. Nutshell does not have a native invoice object; the PDF Document preserves the authoritative billing record. Recurring invoice schedules migrate as Note metadata with next occurrence date and frequency.

Dubsado Contracts migrate as Nutshell Notes on the Contact record with the contract PDF attached as a Document. Contract status, related Client, signature timestamps, and Dubsado signature data migrate as Note body metadata. Nutshell has no native contract object; the signed PDF is the authoritative record. If the contract was created from a Dubsado template, the template name and version are documented in the Note so the customer's admin can identify which templates need rebuilding in Nutshell.

Dubsado Lead Capture Forms store questionnaire responses and link to Projects. We export form submissions with field labels and values as Nutshell Notes on the Contact record. Because Nutshell has no native form submission object, the form field names and response values are serialized into the Note body using a structured template. Custom form field definitions in Dubsado must be mapped to Nutshell Custom Fields on Contact during schema design so future form responses can populate typed fields rather than Notes.

Dubsado Custom Field definitions (type, label, options for dropdown) must be pre-created in Nutshell before Contact migration begins. Dropdown options migrate from Dubsado picklists to Nutshell picklists; multi-select dropdowns map to Nutshell multi-select picklists; text fields map to Nutshell text fields. Value mapping requires destination schema configuration upfront so that Contact import populates typed fields rather than falling back to Note text. We provide a Custom Field mapping matrix during discovery.

Dubsado Time Entries (duration, date, linked Task ID, billable flag) migrate as Nutshell Notes on the Contact record with a structured template capturing duration, date, task reference, and billable status. Nutshell has no native time tracking object. Time entries linked to invoiced work are cross-referenced with the migrated Invoice Note to preserve the billing audit trail. We flag time entry export as a separate CSV extraction during discovery because Dubsado's main CSV export does not include time data.

Dubsado Client Portal access is a per-Client boolean flag with optional portal URL. We migrate the portal access status as a Nutshell Contact Custom Field (portal_active__c: checkbox) and store the portal URL in a text field (portal_url__c) for reference. Nutshell does not have a native client portal feature. If the customer relies on Dubsado client portals for document sharing or approval workflows, we document the portal URLs and contents in the migration handoff so the customer's admin can evaluate Nutshell's document sharing or a third-party portal replacement.

Dubsado Users (Owner, Manager, Team Member roles) are exported with name, email, and role. Nutshell does not have a separate user-as-contact concept. We create a Contact record for each active Dubsado User so the team member's name and email are preserved in the CRM even if they do not correspond to an external client. The Dubsado role is stored as a Note on the Contact for admin reference. Nutshell's own User accounts for the destination platform are provisioned separately by the customer's admin.

Dubsado Workflows cannot be exported. The trigger-condition-action sequences exist only in Dubsado's platform with no documented API export. We cannot migrate Workflows as code. We deliver a Workflow Audit Template that documents every active Dubsado Workflow (trigger, conditions, actions, delays, and CRM objects affected) so the customer's Nutshell admin has a complete specification for rebuilding in Nutshell's native workflow builder. This template is the critical handoff deliverable for the automation rebuild phase.