Migrate from Interactive to Twenty CRM

Quiz-response fields have no native Twenty equivalent

Interactive stores quiz answers as custom fields on contact records. Twenty CRM has no quiz-response field type — these must be created as custom fields on the People object before migration. Field type (text, select, rating) is inferred from the source data, and each quiz question becomes its own custom field. The quiz builder logic itself (question order, branching, scoring rules) does not migrate and must be reconstructed as Twenty workflow conditions or as external automation.

Import order matters for foreign-key resolution

Twenty's CSV import documentation explicitly requires Companies to be loaded before People, and People before Opportunities. Interactive links contacts to companies via a companyId field that must resolve to an existing Twenty Companies record. If contacts are imported before their associated company records, the link breaks and must be corrected manually in Twenty. FlitStack sequences the migration in the correct dependency order and pre-validates that all foreign keys resolve before each batch commits.

Interactive automations and quiz triggers do not migrate

Interactive's workflow engine routes leads based on quiz scores, sends email sequences on quiz completion, and segments lists by quiz-answer conditions. Twenty CRM's workflow builder handles internal record automation (task creation, field updates, notifications) but has no native quiz-trigger mechanism. Automated sequences, score-based routing, and lead-routing rules must be rebuilt either as Twenty workflows or as external automation scripts — FlitStack exports the configuration for reference but cannot auto-convert the logic.

API rate limits affect large bulk operations

Twenty CRM's REST API caps at 100 requests per minute on the Pro tier and 200 per minute on Organization. Interactive exports with 50,000+ records hit this ceiling during batch import unless requests are throttled and batched appropriately. FlitStack manages request pacing, handles 429 responses with exponential backoff, and splits large record sets into chunked batches to stay within rate limits without losing data fidelity.

Many-to-many contact-company associations collapse to primary

Interactive supports N:N contact-to-company associations — a contact can be linked to multiple companies via manual association or domain matching. Twenty CRM's People object links to one primary company via companyId, with additional company associations requiring a custom junction object. FlitStack migrates one primary company per contact (most-recently-modified by default) and surfaces secondary associations for your admin to configure as junction records post-migration.