Migrate from Cirqll to Twenty CRM

Cirqll Customers are the primary contact entity and map directly to Twenty's Person object. We preserve name fields, email, phone, address, and any custom properties as Person fields or custom fields on the Person object. The Person is created before any related Activity or Task so that lookups are satisfied at insert time.

Cirqll Lead records including qualification status, source attribution, and owner assignment map to Twenty's Opportunity object. Lead-to-Customer conversion history is preserved as a linked activity record in Twenty's activity timeline. The qualification status property maps to a custom Opportunity status field.

Cirqll Tasks migrate to Twenty Tasks with due date, assignee, priority flag, and completion status preserved. Both open and completed task states carry forward. Task ownership resolves by matching Cirqll's owner email to a Twenty User record.

Cirqll Activity records — calls, emails, meetings — migrate to Twenty's activity timeline with timestamps, related Contact or Lead reference, and owner attribution. Activity type and duration fields are preserved. We resolve the Person or Opportunity lookup before insert.

Free-text notes attached to Cirqll Contacts or Leads migrate as Note records linked to the corresponding Twenty Person record. Creation timestamp and author attribution are preserved. If notes contain rich text, we strip formatting that Twenty's note renderer cannot display.

Cirqll Calendar events migrate with date, time, title, and attendee list. All-day event flags and recurrence patterns require field-level mapping since Twenty's calendar model handles these differently. Single-occurrence events become Task records; recurring events are flattened into individual instances during migration.

Documents stored in Cirqll are binary blobs exported via a separate download-and-reupload pass rather than the standard API. We preserve original filenames, file sizes, and upload timestamps. File attachments are linked to the corresponding Cirqll Person or Lead record via a lookup in Twenty. Customers should confirm storage limits in their Twenty plan before assuming full parity.

Cirqll User accounts and their assignment to Leads, Tasks, and Activities migrate as owner mappings in Twenty. Active versus inactive status carries forward. Role-based permissions do not transfer because destination permission models differ; we document the original permission structure for the customer's admin to reconfigure in Twenty.

Cirqll custom fields and extended properties on Customer and Lead records are preserved as custom fields on the corresponding Twenty Person and Opportunity objects. We probe the actual field names and types via Cirqll API during scoping since the full schema is not publicly documented. Custom field types map to equivalent Twenty field types during the schema design phase.

Relationships between Cirqll records — a Task assigned to a Customer, an Activity linked to a Lead, a Note attached to a Contact — migrate as typed lookups in Twenty. We resolve parent-record IDs during the migration pass so that relationship integrity is maintained at cutover. Circular or orphaned references are flagged in the scoping report.