Migrate your Dubsado data

Contacts in Dubsado are called Clients. We map First Name, Last Name, Email, Phone, Company, Address, Internal Notes, and Custom Fields. Email is required. Export via CSV or API is straightforward and reliable.

Projects are the central container in Dubsado, linking a Client to their Contracts, Invoices, Tasks, and Forms. We export Project Status, creation date, and all associated child records. Status filter on export is per-page, so we paginate through each status to capture the full dataset.

Dubsado stores contract templates and executed agreements with signature data. We export contract status, related Client, and signature timestamps. The actual contract PDF content and field data require separate file handling — we flag which contracts have e-signatures captured and preserve the audit trail.

We export Invoice ID, amount, status (paid/unpaid/partial), due date, line items, and payment records. Recurring invoice schedules are captured as metadata. Dubsado Payments transaction IDs are preserved to maintain payment history continuity.

Public proposals are a Premier-tier feature only. We export proposal status and linked Client/Project data, but the proposal content body requires separate export. Proposals sent but not yet converted to Projects are flagged separately during scoping.

Forms store questionnaire responses and can be linked to Projects. We export form submissions with field labels and values. Custom form field names map to Dubsado's Custom Field definitions and must be reconciled against the client's field schema before import.

Dubsado supports Custom Fields on Clients and Projects. We export field definitions including type, label, and options. Value mapping requires alignment with destination CRM field types — dropdown options, date formats, and multi-select values often need manual review.

Workflows are not exported via Dubsado's native tools or API. Each Workflow consists of triggers, conditions, and chained actions (emails, tasks, status changes, form sends). We provide a Workflow Audit Template during scoping so customers can document their automations for manual rebuild on the destination platform.

Tasks live within Projects and have assignees, due dates, and completion status. We export task records linked to their parent Project. Full task history including completion timestamps is captured, but assignee activity logs are not separately exportable.

Time tracking in Dubsado is tied to Projects and Tasks. We export time log entries with duration, date, and linked Task ID. Billable time linked to invoices is cross-referenced with Invoice records to ensure accurate financial history preservation.

Client Portal access is a per-Client flag in Dubsado. We export portal access status and portal-specific customizations (banner image, access permissions). The client's portal URL must be mapped to their destination CRM equivalent or regenerated on the new platform.

Dubsado User accounts include name, email, and role (Owner, Manager, Team Member). We export active users and their role assignments. Note that User-to-Contact mapping differs — Dubsado does not merge User and Client records, so owner/manager assignments on Projects require manual reconciliation.

Canned email templates and their merge field syntax are exportable as text. We preserve template body content and subject lines. Merge field mappings vary by destination CRM and must be validated per template after migration.

Dubsado's email inbox connects via IMAP/SMTP and stores threaded communications per Client. Email history is stored in the connected email account, not in Dubsado's database. We cannot export email threads directly — customers must export from their connected email provider separately.

Packages are reusable service bundles that appear on Proposals and Invoices. We export package definitions including name, description, pricing, and included items. Package-to-line-item mapping must be validated against the current Proposals that reference them.