Migrate from Pure Chart to Twenty CRM

Pure Chart contacts map directly to Twenty's People object. First name, last name, email, phone, job title, and address fields translate field-by-field. Pure Chart records without a linked company attach to a default placeholder company or remain unlinked until company resolution runs.

Pure Chart company records map to Twenty's Companies object. Name, domain, industry (as free-text in Twenty), employee count, annual revenue, and address fields carry over. Parent-child company hierarchies in Pure Chart resolve via Twenty's companyId relation field; circular references are flagged during validation.

Pure Chart deals map to Twenty's Opportunities object. Opportunity name, amount, stage, expected close date, probability, and linked company/person relations transfer directly. Stage values map value-by-value; stages that do not exist in Twenty are created as part of the schema preparation phase before migration.

Pure Chart tasks migrate to Twenty's Tasks object. Subject, due date, completion status, assignee (resolved by email match to Twenty workspace members), and linked People/Companies/Opportunities records preserve their original values. Standalone tasks without a parent record land in Twenty's unlinked task view for manual re-association.

Pure Chart notes map to Twenty's Notes object. Note body text, create timestamp, and author (resolved by email match) transfer. Rich-text formatting is preserved where Pure Chart exposes it; plain-text fallback is used when rich-text extraction is unavailable. Notes linked to People, Companies, or Opportunities carry their relation on import.

Pure Chart custom objects migrate 1:1 to Twenty custom objects. The Twenty workspace must have the corresponding custom object schema pre-created with matching field types before migration. Each custom object field in Pure Chart is mapped to its Twenty type-equivalent — text fields to text, number fields to number, pick-lists to select or multi-select.

Pure Chart junction tables connecting two custom objects (many-to-many relationships) become Twenty custom object relation fields. The import sequence matters: both parent objects must exist before the junction records import. We generate a dependency graph from Pure Chart's relationship schema and sequence custom object imports accordingly.

Pure Chart logged emails map to Twenty Tasks with Type='Email'. Call logs map to Tasks with Type='Call'. Meeting records with start/end timestamps map to Twenty Events. Original activity timestamps, owners, and parent-record links (People, Companies, Opportunities) are preserved. Activity text content migrates to the Task/Event body.

Pure Chart file attachments are downloaded from the source, re-uploaded to Twenty's file storage, and linked back to the parent record (People, Companies, Opportunities, Notes) using Twenty's relation field. File size limits and attachment type restrictions are checked before upload to avoid silent import failures.

Pure Chart owner/user IDs resolve by email match against Twenty workspace members. Unmatched owners are flagged with their record count before migration commits. You can invite unmatched owners to the Twenty workspace before migration, or assign their records to a fallback workspace member — the choice is yours and we surface the full unmatched list in the pre-migration report.

Pure Chart workflows, triggers, and sequences do not migrate. Twenty CRM's Pro tier has limited workflow capabilities; the Organization tier offers a fuller workflow builder. We export your Pure Chart workflow definitions as a structured reference document (JSON/YAML) so your admin can rebuild them in Twenty's workflow builder or a third-party automation tool.

Pure Chart reports and dashboards do not migrate. The underlying data (People, Companies, Opportunities, custom objects) migrates completely, so report logic can be rebuilt in Twenty's built-in reporting or any BI tool connected to Twenty's PostgreSQL database. We flag which records contributed to each report so nothing is lost in the rebuild.