Migrate from SuiteDash to Twenty CRM

SuiteDash Contacts map directly to Twenty People records. We extract all standard Contact fields (name, email, phone, address, job title) and any Contact-scoped custom fields. Primary Contact and Secondary Client assignments on Projects transfer as related record links. Email opt-in status maps to Twenty's custom field for consent tracking. The SuiteDash Contact ID is stored as a legacy identifier on the Twenty Person record for reconciliation.

SuiteDash Public Company records map to Twenty Company with full fidelity. Company Public custom fields migrate as Twenty custom fields on the Company object. The Company ID is stored as a legacy identifier for relationship resolution during Contact import. Multi-company associations on Contacts (Circles in SuiteDash) are preserved as tag labels on the Twenty Person record.

SuiteDash Private Company records present a visibility challenge because Private custom fields are only visible to the Primary Contact and are not exposed via Dynamic Data Placeholders. We identify all Private-scoped Company fields during scoping, separate them from Public fields, and discuss with the customer whether they should map to public Twenty custom fields or be stored as custom note fields with restricted visibility managed through Twenty's workspace permissions. Data that cannot be placed in an equivalent visibility model is flagged for manual review.

SuiteDash Deals map to Twenty Opportunities with pipeline stages preserved as Opportunity stage values. The HubSpot-style dealstage property migrates to Twenty's stageName. Probability percentages, Won/Lost status, close date, and deal value transfer as typed Opportunity fields. If SuiteDash Deals reference multiple pipelines, each pipeline becomes a Twenty Sales Process or Custom Object with its own stage set, depending on Twenty's current multi-pipeline support.

SuiteDash Projects map to a Twenty Custom Object named Projects. Project-level custom fields migrate as Twenty custom fields on this object. Tasks within Projects migrate as Twenty Tasks linked to the parent Projects Custom Object via a lookup relationship. Primary Client and Secondary Client assignments on Projects are resolved by linking to the corresponding Twenty Person records (created from SuiteDash Contacts in step 1). We preserve parent-child task hierarchy through ordered sequence numbers in a custom field.

SuiteDash Support Tickets migrate to a Twenty Custom Object named Tickets. Ticket status workflows (Open, In Progress, Resolved, Closed) map to picklist values in Twenty. Conversation threads migrate as Note records linked to the Ticket Custom Object, with each message preserved as a separate Note entry with author and timestamp. Custom fields on tickets migrate as Twenty custom fields on the Tickets object.

Invoice records migrate to a Twenty Custom Object named Invoices. SuiteDash Invoice Custom Fields (which are a distinct field type not available via GET /contact/meta) are captured during Invoice-specific scoping and mapped to Twenty custom fields on the Invoices object. Historical paid invoices migrate as read-only records. Active or pending invoices requiring workflow actions are flagged for the customer to handle post-migration. Line items migrate as a JSON-encoded custom field or as a related Custom Object depending on complexity.

SuiteDash Appointments migrate to Twenty Event records. Scheduling data, associated Contacts, status, and location transfer. Bidirectional calendar sync settings (Google Calendar, Outlook) do not port and are flagged for manual reconfiguration in Twenty. Booking page configurations also do not migrate and require rebuild in Twenty's workspace settings.

SuiteDash Staff records map to Twenty Members. Role assignments migrate to Twenty workspace roles. Owner and assignee references on Deals, Projects, and Tickets resolve by matching Staff email to the corresponding Twenty Member record created during this step. Staff-level custom fields migrate as Twenty custom fields on the Member record.

SuiteDash Organization-level custom fields and settings are account-scoped. These migrate as Twenty workspace-level custom fields accessible via Settings. White-label settings, branding configurations, and role definitions require manual reconfiguration in Twenty. We document the full Organization settings set during scoping for the customer to recreate.

SuiteDash Custom Fields exist at six scopes: Contact, Company Public, Company Private, Organization, Staff, Work Request, Project, and Support. We export the full schema via GET /contact/meta and run an Invoice-specific field discovery to capture Invoice Custom Fields separately. Each field is mapped to the corresponding Twenty object (Person, Company, Custom Object, Member) and pre-created in Twenty before data import begins. Fields must exist in Twenty before any CSV import; we create them via Twenty's Settings Data Model interface during the schema setup phase.

SuiteDash tags on Contacts and Companies migrate as Twenty Tags. Tags used for segmentation or Circles associations become comma-separated label lists on the Twenty Person or Company record. The customer chooses at scoping whether to use native Twenty Tags (for CRM-level labeling) or multi-select picklist fields (for structured categorization).