Migrate from TeamSystem CRM to Twenty CRM

TeamSystem Contact records map to Twenty People. The TeamSystem contact identifier is preserved as an external ID in Twenty for future sync and deduplication. Email, phone, address, job title, and department fields map directly to Twenty's standard People fields. Owner assignment maps via email match to Twenty Members (users). Where TeamSystem contacts are linked to a Company record, the link resolves to the Twenty Company via the Company external ID built during the Companies phase.

TeamSystem Company records map directly to Twenty Company. The domain field from TeamSystem populates the Website field in Twenty. Company type, industry, employee count, and annual revenue map to the corresponding Twenty fields where they exist; custom fields require pre-creation in Twenty's Data Model before import. Company records are imported before People records so that the relationship lookup is satisfied at Contact import time.

TeamSystem Lead records with status and source fields map to Twenty People. Since Twenty does not have a separate Lead object, unqualified prospects live as People records alongside converted contacts. We preserve the original Lead status as a custom field lead_status__c on the People record. If the customer uses a strict lead qualification workflow, we recommend creating a custom People type or tag to distinguish unqualified from qualified records.

TeamSystem Opportunity records map directly to Twenty Opportunity. Pipeline stage names and probabilities are preserved through explicit field mapping. Stage ordering is maintained by setting the position field in Twenty. The opportunity amount maps to the amount field, and the expected close date maps to the closeDate field. Owner assignment resolves via email match to the Twenty Member provisioned during the users phase.

TeamSystem pipeline definitions (stage names, probabilities, sequence) require configuration in Twenty. Since Twenty's pipeline model uses Opportunity stages rather than separate Pipeline objects, we create the stage values in Twenty's Data Model under Opportunity before importing deal records. Custom stage names map directly; probability percentages round to integers as Twenty allows.

TeamSystem Activity records of type call and task map to Twenty Task. Activity records of type email and meeting map to Twenty Note or Task depending on whether they represent a logged interaction (Note with body) or an action item (Task with due date). Call duration and disposition map to custom Task fields. The original activity timestamp maps to the due date or a custom activityDate field in Twenty for timeline ordering. Activity type taxonomy differs significantly between platforms, so we build a type-mapping table during scoping.

TeamSystem organization-specific fields on Contacts, Companies, and Opportunities require pre-creation in Twenty's Settings → Data Model before any CSV import. We extract the full field registry from TeamSystem during scoping, identify which fields are actively used (not deprecated or test fields), and create matching custom fields in Twenty with the appropriate type (text, number, date, select, multi-select). Fields that do not exist in Twenty at import time are silently skipped by the CSV loader.

TeamSystem custom objects migrate to Twenty Custom Objects with equivalent API names. We pre-create the destination schema in Twenty including all custom fields, lookup relationships, and any picklist options before data import. Custom object records are imported last because they often have lookup fields pointing to standard objects (Company, People, Opportunity) that must already exist.

TeamSystem User accounts with role assignments and record ownership map to Twenty Members. User IDs in TeamSystem do not map directly to Twenty Member IDs, so we build a mapping table during scoping matching TeamSystem user email to Twenty Member email. All Twenty Members must be provisioned and active before importing any records with owner references; otherwise the ownership relationship cannot be resolved and those records are held in a reconciliation queue.

Email history linked to contacts in TeamSystem exports as activity records with body content. These migrate to Twenty Note records linked to the corresponding People record via the contact's external ID. Full inbox association data (folder structure, read/unread status) does not transfer; only the email body and timestamp are preserved. We flag email integration reconfiguration as a post-migration step for the customer's admin.

Files linked to deals and contacts in TeamSystem export by reference URL or direct download. We extract attachment URLs during the export phase and include them in the migration package. File storage limits and attachment expiry rules must be checked per organization before migration. Attachments are imported as linked records with the URL preserved as a custom field pointing to the original document location.