Migrate from SmartDesk to Twenty CRM

SmartDesk Leads map to Twenty Persons flagged with a custom role field (lead_status or person_type) set to 'Lead'. We preserve SmartDesk Lead Source and Lead Status as custom fields on the Twenty Person object. Since Twenty uses a single Person object for all contact types, we do not create a separate record type; instead we add a person_type custom field and set the value to 'Lead' for all migrated Lead records. The customer must pre-create the person_type custom field and its picklist values (Lead, Contact, Customer) in Twenty before migration runs.

SmartDesk Contacts map directly to Twenty Persons. Standard SmartDesk fields (name, email, phone, address) map to Twenty's standard Person fields. Custom contact properties migrate as custom fields on the Person object. We flag the person_type as 'Contact' or 'Customer' based on SmartDesk's lifecycle stage where applicable. Custom fields must be pre-created in Twenty before migration.

SmartDesk Accounts (also labeled Companies) map directly to Twenty Company records. The company domain becomes the Website field. Industry classification, employee count, and any custom properties attached to the Account migrate as custom fields on the Company object. We create Company before any Person import so that the Person-to-Company relationship is resolved at insert time.

SmartDesk Deals map to Twenty Opportunities. Deal name, value, expected close date, and owner migrate to Twenty Opportunity fields. Stage values require reconciliation: SmartDesk allows fully custom pipeline stages per account, while Twenty uses a standard stage set defined in workspace settings. We enumerate the SmartDesk pipeline stages during scoping, map each to the nearest Twenty stage equivalent, and flag any stages that require new custom stage values to be created in Twenty before import.

SmartDesk Pipelines contain ordered stages defining the sales process. Twenty uses a standard Opportunities pipeline with configurable stages. We map pipeline names and stage sequences but must reconcile stage counts and naming between source and destination. Any SmartDesk pipeline stages that have no Twenty equivalent are pre-created in Twenty's pipeline settings before Deals import begins. The customer configures pipeline stages in Twenty admin settings; we provide a stage-mapping manifest listing every SmartDesk stage and its proposed Twenty counterpart.

SmartDesk Tasks attached to Contacts or Deals map to Twenty Tasks with assignee, due date, status, and description preserved. We map the task owner by email lookup against the User mapping and preserve the linkage to the parent Person or Opportunity. Tasks are imported after Persons and Opportunities so that parent-record resolution succeeds.

SmartDesk Activities (calls, emails, meetings, notes logged against Contacts or Deals) map to Twenty Task records for calls and tasks, and Event records for meetings. Email content migrates to the Task body or a linked Note. Activity timestamps are preserved to maintain the timeline ordering. We link each activity to its parent Person or Opportunity via the activity's relationship field. Custom activity metadata migrates to custom fields on the Task or Event object after pre-creation.

SmartDesk Users and Owners map to Twenty WorkspaceMembers. We match by email address. Any SmartDesk Owner without a matching Twenty WorkspaceMember is held in a reconciliation queue for the customer to provision before record import resumes. Active status and role information migrate as WorkspaceMember properties.

SmartDesk Campaigns (name, type, status, start and end dates) migrate to a Twenty custom object named Campaign if the customer requires campaign tracking in the new system. We create the Campaign custom object via the /metadata API before data import. Email send and open tracking data is not migrated as it lives in the email delivery system rather than in SmartDesk's CRM data layer. We document the campaign metadata and recommend post-migration campaign tracking configuration in Twenty's settings or via a third-party integration.

SmartDesk Tickets migrate to a Twenty custom object named Ticket if the customer continues to use help desk functionality. We create the Ticket custom object via the /metadata API, including custom fields for priority, status, assignee, and linked contact. Conversation threads migrate as Note records linked to the Ticket. If the customer does not require ticket tracking in Twenty, we export the ticket data as a CSV deliverable for archival purposes.

File attachments associated with Contacts, Deals, or Tickets are downloaded from SmartDesk and re-uploaded to Twenty. We handle file type validation and preserve original filenames. Attachments are linked to the parent record (Person, Opportunity, or custom Ticket object) via Twenty's attachment relationship.