Migrate from ASPEC to Twenty CRM

ASPEC Contact records (name, email, phone, address, owner assignment) map directly to Twenty CRM's Person object. We extract every Contact field including per-user custom fields enumerated during schema discovery and write them as typed fields on the Person record. The email address serves as the dedupe key during import. ASPEC owner assignment maps to Twenty's workspaceMember field resolved via the User mapping step.

ASPEC Company records map directly to Twenty's Company object, preserving the link to associated Contacts and Opportunities. The domain from ASPEC's company data becomes the Website field in Twenty. We create Companies before Person records during import so that the company-to-person relationship is satisfied at Person insert time.

ASPEC Opportunity records (deal name, value, stage, expected close date) map to Twenty CRM Opportunity. The stage name from ASPEC maps directly to Twenty's stage field, but any custom ASPEC stage labels require value-mapping to Twenty's pipeline stage enum before import. ASPEC's pipeline association maps to Twenty's pipeline field, which we configure during the schema setup phase.

ASPEC pipelines define stage names and ordering in a separate configuration layer. We capture the full pipeline configuration during the schema discovery step, then create matching Twenty CRM pipelines and stage definitions via the Twenty metadata API before Opportunities are imported. Stage probabilities migrate from ASPEC if available and are set on the corresponding Twenty stage record.

ASPEC call activity records (timestamped, linked to Contact or Company) map to Twenty Task records with type = call. Call disposition and duration transfer to custom Task fields if defined in the Twenty schema during setup. Activity timeline ordering is preserved by setting the createdAt timestamp to the original ASPEC activity timestamp.

ASPEC email activity records map to Twenty Task with type = email and the email body preserved in the Task description field. The linked Contact or Company from ASPEC resolves to the Twenty Person or Company record at migration time using the email address or record ID cross-reference.

ASPEC meeting records map to Twenty Task with type = meeting, preserving location, start time, and end time. Attendees from ASPEC are recorded in the Task's linked-people field or as a custom multi-select field in Twenty, depending on the schema configuration decided during scoping.

ASPEC task activity records (status, priority, due date, owner) map to Twenty Task records with type = task. Status and priority from ASPEC map to Twenty's status and priority enums. Task owner assignment resolves via the User mapping step using the ASPEC owner email as the match key.

ASPEC stores per-user custom field definitions in a separate metadata layer. We run a mandatory schema discovery step before any data migration, enumerating all active custom fields, their data types, and which objects they are attached to. We then pre-create the matching custom field definitions in Twenty CRM's schema via the /metadata API before record import begins. Skipping this step means custom fields are silently absent from migrated records.

ASPEC tags on Contacts and Companies migrate as multi-select picklist fields in Twenty or as tagged-objects depending on the customer's preferred organization strategy. We capture all distinct tag values during schema discovery and configure the target field type during the schema setup phase. The customer chooses the tag strategy during scoping.

ASPEC record ownership assigns to Users, which we map to Twenty CRM workspaceMembers. We resolve ASPEC owners by email match against Twenty User records created during setup. Any ASPEC owner without a matching Twenty user is held in a reconciliation queue for the customer to provision before record import resumes. Archived or inactive ASPEC users require explicit reactivation decisions from the customer.