Migrate from Dubsado to Mailchimp

Dubsado Clients map directly to Mailchimp Contacts within a target Audience. We map First Name, Last Name, Email, Phone, Company, and Address fields to their Mailchimp equivalents. Email is the required dedupe key. Dubsado Client custom fields (short-text and date types) map to Mailchimp merge fields; text fields become TEXT merge fields, date fields become DATE merge fields. Multi-select dropdown custom fields cannot map directly to Mailchimp dropdown merge fields because Mailchimp does not support multi-select at the field level; we flatten these to TEXT merge fields or split into multiple single-select tags.

Dubsado Projects do not have a Mailchimp equivalent. We extract the project status from each Dubsado project record and apply it as a Mailchimp tag on the linked Client contact (for example, tag 'Project: Active', 'Project: Completed', 'Project: Archived'). This preserves Dubsado project status segmentation inside Mailchimp's tag taxonomy. Projects without a linked Client record are flagged as orphaned and held for manual review. The project creation date and project title are optionally stored as merge fields if the customer wants to preserve that granularity.

Dubsado Invoices (ID, amount, status, due date, line items, payment records) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not store or generate financial records. We export Invoices as a structured CSV file alongside the migration for the customer to archive in their accounting system. Dubsado Payments transaction IDs are preserved in the CSV for Stripe reconciliation if the customer uses Stripe separately.

Dubsado Contracts (status, related Client, signature timestamps, PDF content) do not have a Mailchimp equivalent. We export contract metadata (client name, contract status, signature date, template used) as a CSV record. The PDF document content does not transfer to Mailchimp. We recommend the customer store original contract PDFs in Google Drive, Dropbox, or a document management system and link to them from the CSV if needed.

Dubsado Public Proposals are a Premier-tier feature. Proposal status and linked Client/Project data are exportable; proposal content body requires separate export. Mailchimp does not support proposal documents. We export proposal metadata to CSV. Note that if the customer's Dubsado plan is downgraded after migration, proposal records remain accessible via Dubsado export but the platform's proposal tools become unavailable.

Dubsado Lead Capture Form submissions map to Mailchimp Contact records within the target Audience. Form field labels and submitted values transfer as merge field data where field types are compatible. The form template itself (layout, branding, logic) does not migrate; we recommend Mailchimp's built-in signup form builder or an embedded form service as the replacement. Form submissions linked to a Dubsado Project inherit the project's tag in Mailchimp to preserve source context.

Dubsado Custom Mapped Fields (Client-level and Project-level) are exported as field definitions including type, label, and options. We pre-create matching Mailchimp merge fields in the target Audience before contact import. Short-text Dubsado fields map to Mailchimp TEXT merge fields. Date Dubsado fields map to Mailchimp DATE merge fields. Dropdown options become Mailchimp dropdown merge field values. Multi-select options cannot map to Mailchimp multi-select; we discuss tag-based alternatives with the customer during scoping.

Dubsado Workflows cannot be exported. Workflows consist of triggers (project status change, form submission, payment received), conditions (client field values, project type), and chained actions (email send, task create, status update). These definitions are not accessible via CSV or API. We provide a Workflow Audit Template during scoping that the customer's team fills in manually, documenting every trigger, condition, and action for rebuild inside Mailchimp Customer Journeys post-migration. This is not a migration of automation logic but a documentation exercise.