Migrate from Glaze CRM to Twenty CRM

Glaze CRM Contact records map to Twenty CRM Person objects. Standard fields (name, email, phone, company association) map directly. Glaze CRM's custom contact fields require type inference from a sample export — multi-select fields must be identified and remapped to Twenty's multi-select or tag structure. We sequence Person import after Company so that the workspaceId lookup resolves at insert time.

Glaze CRM Company records map directly to Twenty CRM Company objects. Address data, industry tags, and related contacts transfer with field-level mapping. Glaze CRM Companies are the parent of Contacts and Deals, so we import Companies first in every migration phase. The company domain from Glaze CRM's website field maps to the domain field in Twenty.

Glaze CRM Deal records map to Twenty CRM Opportunity objects. Deal name, amount, stage, and associated company or contact transfer. Pipeline stages are organizational-level in Glaze CRM and must be reconciled against Twenty's opportunity stage configuration before migration. We document existing Glaze CRM stage names and probabilities for the customer's admin to configure in Twenty's settings.

Glaze CRM Lead records — which are separate from Contacts in Glaze CRM — map to Twenty CRM Person records flagged as leads. Lead source, status, and owner assignment transfer to Twenty's person fields. We preserve the Glaze CRM lead status in a custom field for audit. If Twenty's data model uses Persons for both leads and contacts, we flag this during scoping.

Glaze CRM pipeline and stage configurations are organizational-level settings. We document every stage name, probability, and pipeline assignment from the source instance and deliver this as a configuration guide for Twenty's admin to implement. Pipeline structures do not migrate as configuration code — the rebuild is in scope for the customer's team.

Glaze CRM Task records (subject, due date, assignee, status, linked entity) map to Twenty CRM Task objects. Completed vs. open status flags transfer. Task associations to Contacts, Deals, or Companies are remapped using the resolved Twenty record IDs from the parent import phases.

Glaze CRM custom fields on any object require a custom field inventory built from a sample export. Multi-select fields need special handling — we identify the delimiter used in Glaze CRM and map to Twenty's multi-select or tag structure. We pre-create all custom fields in Twenty's schema before any data import begins.

Glaze CRM Users who own records map to Twenty CRM workspace users resolved by email address match. Inactive Glaze CRM users with no record assignments can be excluded. Active users without a matching Twenty account go to a reconciliation queue for the customer's admin to provision before the Opportunity and Task import phases begin.

Glaze CRM tags stored on Contacts, Companies, or Deals migrate as flat string arrays applied to the corresponding Twenty records. Tags do not carry their own metadata. We deduplicate tags at transform time to avoid inflating the target tag list.

Glaze CRM document attachments do not expose a documented file export API. We migrate document metadata — filename, upload date, linked record — as structured reference records in Twenty. The actual file binaries must be re-uploaded manually or through a separate file transfer arranged with the customer.