Migrate from Cloze to Twenty CRM

Cloze People map directly to Twenty Person records. All standard properties (name, email, phone, address, social links) transfer to Twenty's Person fields. Custom fields on the Cloze Person migrate to custom fields on Twenty Person created during the pre-migration schema design phase. We resolve the Stage assignment (Lead, Potential, Active, Inactive, Lost) as a tag or multi-select field on Person since Twenty does not have a native Stage property on Person.

Cloze Companies map one-to-one to Twenty Companies. Address, industry, website, and social fields transfer directly. The Company-Person relationship (Cloze's link between People and Companies) migrates as a Twenty Company-Person workspace membership or a manual link in the migration notes depending on Twenty's current relationship model at migration time.

Cloze's Projects, Deals, and Properties (interchangeable aliases in Cloze) map to Twenty Opportunities. The Stage (Potential, Active, Done, Lost) migrates to Twenty's Opportunity stage field, and we normalize any real estate-specific stage labels (Property Listed, Offer Made, Under Contract) to neutral pipeline values during transformation. Custom fields on the Cloze Project migrate to custom Opportunity fields in Twenty.

Cloze's pipeline stages (Lead, Potential, Active, Inactive, Lost) map to Twenty's Opportunity pipeline stages. We configure the Twenty pipeline with stages that match the customer's actual Cloze usage, stripping any real estate-specific stage names (e.g., Listing, Offer, Closing) and replacing them with neutral equivalents. Stage probabilities transfer as a configuration in Twenty's pipeline settings.

Cloze Segments and Audiences (contact groupings by stage or custom criteria) migrate as either a multi-select picklist custom field on Twenty Person or as Topics with TopicAssignment records, depending on the customer's usage pattern. If Segments are used as audience lists for campaigns, we recommend Topics; if they represent a contact property (e.g., Lead Source, Account Type), we recommend a custom multi-select field. The customer chooses during scoping.

Cloze Timeline entries (emails, calls, texts, meetings, notes) migrate to Twenty activity records linked to the corresponding Person or Company. We preserve the activity type, timestamp, and content where Cloze retained the full record. Email body content migrates as a Note or Comment record attached to the Person; calls and meetings migrate as Task or Event records. Raw email content completeness depends on what Cloze retained from the connected Gmail or Outlook account.

Cloze Tags (flat labels on People and Companies) migrate as a multi-select custom field on Twenty Person or Company. If the customer uses tags for content or deal categorization, we recommend Twenty Topics as the equivalent classification system. Tags with fewer than 50 distinct values map to a multi-select picklist; tags with high cardinality (thousands of unique values) map to a text field as a comma-separated string for post-migration review.

Cloze custom fields on People, Companies, and Projects map to Twenty custom fields on Person, Company, and Opportunity. We create the destination custom fields during the pre-migration schema design phase using Twenty's Settings > Data Model or the Twenty SDK defineObject syntax. Field types (text, number, date, choice) map directly; multi-select choice fields require a custom field in Twenty.

Cloze Teams control access and assignment. We preserve team membership by mapping each Cloze team to a Twenty workspace membership or role assignment, noting that the destination must have matching team structures for assignment routing to remain functional. If Twenty's role model differs from Cloze's at migration time, we deliver a written mapping recommendation.

Cloze Campaigns (Business Platinum only) migrate as custom records in Twenty with campaign name, type, trigger conditions, and target audience preserved in a written definition document. The campaign automation logic does not execute in Twenty because Cloze Campaigns and Twenty's workflow builder are different automation models. We deliver the campaign schema as a JSON manifest and a written rebuild guide for the customer's admin.