Migrate from APTANIA CRM to Twenty CRM

APTANIA Contacts map to Twenty Person records. APTANIA's B2C/B2B type flag (stored as a custom property) migrates as a custom field or tag on the Twenty Person record. Standard fields (name, email, phone, address) map directly; lifecycle stage from APTANIA maps to a custom field for audit. Person is created after Company (if B2B) so that any Company linkage is resolved at import time.

APTANIA Company records map 1:1 to Twenty Company. Company is imported first in the dependency chain because Contact and Deal records hold a required or optional Company lookup. Domain from APTANIA's company domain field maps to Twenty Company domainName. APTANIA's B2B relationship model (one-to-many with Contacts) maps directly to Twenty's Company-Person relationship.

APTANIA Deals map to Twenty Opportunity. We extract dealstage, monetary value, close date, and any associated Contact or Company ID from the export. Pipeline and stage names from APTANIA are inferred from exported deal records since the stage-object relationship is not publicly documented; we reconstruct these as Twenty Pipeline and Stage records before Opportunity import and map stage labels by name match.

APTANIA pipeline structure is inferred from exported Deal records by enumerating unique pipeline and stage values. We create matching Pipelines in Twenty and configure Stage records with the appropriate names and ordering before Opportunity import. If APTANIA uses a single default pipeline, we create one Pipeline in Twenty; multi-pipeline APTANIA accounts map to multiple Twenty Pipelines with corresponding Record Type filters.

APTANIA activity logs (emails, calls, meetings, notes) exist but the export schema is not publicly documented. We extract all available activity records from export files and map them to Twenty Task (for calls and generic activities), Event (for meetings with start/end timestamps), and Note (for note-type engagements). The source activity type field is preserved as a custom field on the Twenty record for reconciliation. We flag any activity records with unresolvable parent-record references (Contact or Company ID not found in export) and report them separately for manual review.

APTANIA custom fields are exported with their values but the field metadata (type, required flag, picklist options) is not fully exposed in the export schema. We export field names and values, infer field types from data inspection (text, number, date, boolean), recreate equivalent custom fields in Twenty's workspace via API before record import, and map values directly. Any ambiguous field types are flagged for customer confirmation during scoping.

APTANIA users are exported by email and mapped to Twenty users by email match. Role and permission structures differ across platforms; we preserve the APTANIA role name as a custom field on the Twenty User record for manual permission configuration post-migration. Any APTANIA user without a corresponding Twenty account is held in a user reconciliation queue for the customer's admin to provision before record import continues.

APTANIA's trigger-based email automation rules (trigger on activity, trigger on inactivity, time-delayed sends) are not accessible via export. We do not migrate automation logic. As part of pre-migration preparation, we request that the customer document all active automation rules with screenshots so they have a reference guide for rebuilding triggers in Twenty's workflow system. We flag this gap in the data map before migration begins.

APTANIA's web traffic monitoring data (channel attribution, referrer, UTM parameters, landing page history) is stored in APTANIA's tracking system and does not export to standard file formats. We do not migrate web tracking events. We flag this gap in the data map and recommend that the customer configure fresh web tracking integration (via Twenty's integrations or a third-party tool) before go-live to preserve future attribution data.

APTANIA uses a B2C/B2B flag on the Contact record to distinguish record types within a unified Contact object. In Twenty, B2B contacts are Persons linked to Company records (via the company link field) and B2C contacts are Persons without a Company link. We apply this distinction at migration time: Contacts with B2B flag receive a Company link; Contacts with B2C flag are imported as standalone Persons. This transformation is validated against the exported Contact-Company relationship data.