Migrate from Aritic Sales CRM to Twenty CRM

Aritic Company records map directly to Twenty Company records. Company name, address, industry, size, and website fields map 1:1. Multi-currency settings on Aritic Professional transfer as a custom field in Twenty since Twenty supports currency fields through configuration. We import Companies first to establish foreign-key relationships for downstream Person record imports.

Aritic Contact records map to Twenty Person records with name, email, phone, and job title transferred directly. Aritic's flexible relationship model allowing any Contact to link to any unrelated Company translates as secondary Company associations on the Twenty Person record. We preserve the relationship as a custom field note and flag any Person with more than one associated Company for manual verification post-import.

Aritic Deals map to Twenty Opportunity records with deal name, value, stage, probability, and milestone history preserved. Multi-currency deal values map to Twenty's currency fields. Closed-won and closed-loss reasons from Aritic custom fields become Opportunity custom fields in Twenty. The deal stage history is carried forward as a custom text field for audit purposes.

Aritic Pipelines (multiple supported on all plans) map to Twenty Pipelines. Stage names, ordering, and win/loss criteria transfer. Pipeline-level automation triggers attached to stages are flagged as workflow gotchas for the customer to rebuild post-migration in Twenty's automation framework.

Aritic Tasks linked to Contacts or Deals migrate to Twenty Tasks with due dates, assignees, and completion status preserved. Open and closed tasks transfer; completed task history is preserved but the full activity log depth may not carry forward depending on Aritic's API export capabilities at the time of migration.

Aritic Activity records (calls, emails, meetings) logged against Contacts or Deals map to Twenty Activity records with type, date, duration, and notes preserved. Activity timeline ordering is maintained by resolving parent-record lookups (Person, Company, Opportunity) during the transformation step. We merge Aritic's activity types into Twenty's activity model while preserving the full context against the correct record.

Aritic lead scores export as static numeric values at migration time and land in Twenty as a custom number field on the Person record. The active scoring rule logic (rules, weights, triggers) is not portable. We provide a scoring-rule inventory sheet during discovery so the customer can reconstruct their model in Twenty, estimating 1-2 hours per complex scoring rule.

Aritic File Manager documents and deal-related files export as individual downloads, bundled into a ZIP organized by Person and Opportunity ID for re-import. Some attachments in Aritic are stored as URLs pointing to external file storage rather than as binary blobs; we detect these URL-based attachments during the export scan, download referenced files into the migration bundle, and flag any broken external links for manual resolution.

Aritic Invoice records (line items, totals, currency, payment status) map to Twenty as custom object records or as PDF attachments linked to the Opportunity, depending on Twenty's invoice object support at the migration time. Multi-currency invoices require explicit currency field mapping. E-contract signatures and quote documents migrate as PDF attachments with signature status preserved as a custom property in Twenty.

Aritic User records (name, email, role) map to Twenty User records. Owner assignments on Deals and Tasks migrate by resolving the Aritic user email against the Twenty User table. Inactive Aritic users are preserved as read-only records to maintain historical accuracy of past assignments. Missing Twenty Users are held in a reconciliation queue for the customer to provision before record import resumes.

Custom fields added by the customer on Persons, Companies, or Opportunities are enumerated during scoping. Each custom field is mapped explicitly to its Twenty custom field equivalent. Any custom field with a picklist, formula-type behavior, or conditional logic is flagged for manual configuration in Twenty before the migration runs, because these cannot be automatically translated between platforms.

Tags applied to Contacts and Deals in Aritic export as a comma-separated list and map to Twenty's tagging or label system on the Person and Opportunity records. Segmentation rules built in Aritic do not export and must be rebuilt as Twenty filters or segments post-migration. The customer chooses the tag strategy during scoping based on whether they prefer flat tags or hierarchical segments.