Migrate from Apto to Twenty CRM

Apto's Person records map to Twenty's People object. First name, last name, email, phone, and job title transfer as direct field mappings. Each Person's company association becomes the companyId relation pointing to the matching Company record in Twenty. We validate email format uniqueness and flag duplicate email addresses before migration to prevent data integrity issues in Twenty.

Apto's Organization object maps to Twenty's Companies object. Company name, domain, industry, employee count, and annual revenue translate directly. Parent-child company hierarchies in Apto map to the parentCompanyId relation in Twenty for multi-entity organizations. We validate that parent companies exist in Apto before mapping hierarchical relationships to avoid orphaned company records.

Apto Deals map to Twenty Opportunities with deal name becoming opportunity name, deal amount mapping to amount, and close date becoming closeDate. Pipeline and stage values in Apto undergo value mapping to match Twenty's stage pick-list options. We validate stage name mappings against Twenty's available stage options and flag any non-matching stages for configuration before migration.

Apto pipeline stage names map one-to-one to Twenty Opportunity stage pick-list values. Stage probability and forecast category are re-applied in Twenty based on your specified stage configuration. Stage-entered timestamps migrate as custom datetime fields for historical reporting continuity. We document your Apto stage sequence and probability settings for reconfiguration in Twenty's pipeline settings.

Apto's activity log entries — calls, emails, meetings, and notes — map to Twenty's Task object with Type set to 'Call', 'Email', or 'Meeting' respectively. Original timestamps, owners, and parent record links (personId, companyId, opportunityId) are preserved to maintain the activity timeline in Twenty.

Apto notes migrate as Twenty Notes attached to the relevant People, Company, or Opportunity record via the noteTargetId relation. Rich-text formatting in Apto notes is preserved where the format is compatible with Twenty's note rendering. We convert incompatible formatting to plain text to ensure readability, and we validate that all note-target relationships resolve correctly before migration completes.

Apto custom objects map one-to-one to Twenty custom objects. The custom object schema must be pre-created in Twenty Settings → Data Model before migration. Custom object associations using Apto's N:N relationship model need junction objects in Twenty. We create junction object schemas and define the many-to-many relationships during the schema preparation phase.

Apto owner IDs are resolved by email match against Twenty workspace members. Unmatched owners are flagged before migration; their records can be assigned to a fallback Twenty user or imported without an owner assignment for later manual routing. We generate an owner resolution report listing all matched and unmatched owners with their Apto record counts for your review.

Apto file attachments do not transfer via CSV export. We re-upload files to Twenty's storage layer via the API or manual re-upload, linking them to the parent record. This step adds to migration time for heavily-attached accounts. We provide a file inventory report listing each attachment with its parent record type and ID for manual re-upload tracking.

Apto workflows, sequences, and automation rules have no direct equivalent in Twenty's workflow builder and must be rebuilt. We export Apto workflow definitions as a structured JSON reference document to accelerate the Twenty rebuild. The export includes trigger conditions, action steps, time delays, and conditional branching logic from your Apto workflows.

Apto reports and dashboards do not transfer. The underlying data in Opportunities, Notes, and Tasks migrates fully. Your Twenty admin rebuilds reports using Twenty's analytics views and custom dashboards. We document your Apto report configurations including filters, groupings, and chart types as a reference for the Twenty rebuild.

Apto role-based access controls and sharing rules do not migrate. Twenty's role and permission system uses different primitives. We document your Apto permission structure including role definitions, permission sets, and sharing rule configurations as a reference for your Twenty admin to reconfigure the access control setup.