Migrate from Entera to Twenty CRM

Entera person records map directly to Twenty's People object. Full name, email, phone, job title, and address fields map field-for-field. Owner (assignee) maps via email resolution against Twenty Workspace Members. Primary company association maps as a relation to the Twenty Companies record.

Entera company or account records map to Twenty's Companies object. Company name, domain (website URL), industry, employee count, and annual revenue map to Twenty's standard Company fields. Parent-company hierarchies in Entera map to the Twenty Company relation field for subsidiary structures.

Entera deal records map to Twenty Opportunities. The deal name becomes Opportunity name; deal amount maps to the amount field; deal stage maps to Twenty stage values via value mapping. Property-specific fields (address, property type, acquisition cost) migrate as custom fields on the Opportunity since Twenty has no native real-estate deal model.

Entera pipeline stages map to Twenty's Opportunity stage pick-list. Each Entera stage value (e.g. Prospecting, Under Review, Won, Lost) is mapped to a matching Twenty stage option. Stage probability percentages that exist in Entera are preserved as a custom field in Twenty since Twenty does not expose stage-level probability natively.

Entera tasks and activity records map to Twenty's Task object. Subject, description, due date, completion status, and assignee resolve via email match against Twenty users. Completed-at timestamps are preserved as a custom datetime field since Twenty Task does not natively track completion history.

Entera note records map to Twenty Notes attached to the relevant People, Company, or Opportunity record. Note body and create date map directly. If Entera notes contain rich-text formatting, Twenty's Note object stores plain text with formatting simplified to plain paragraphs.

Entera email, call, and meeting records that exist as standalone engagement objects in Entera are disaggregated: calls become Twenty Tasks with Type='Call'; emails become Tasks with Type='Email'; meeting records become Notes with a timestamped entry. The original engagement timestamp and owner are preserved in the mapped Twenty record.

Any Entera custom contact properties not present in Twenty's standard People fields require a custom field to be created in Twenty Settings → Data Model before import. FlitStack creates these as text, number, select, or multi-select fields based on the source property type. Custom field names are preserved verbatim from Entera.

Real-estate deal fields unique to Entera (e.g. property type, acquisition date, investment source, ARV estimate) migrate as custom fields on Twenty Opportunities. These must be pre-created in Twenty's data model under Settings → Data Model before the deal import runs. Each field's type is matched to Twenty's supported types.

If Entera contains custom objects (e.g. Properties, Investors, Fund Records), these map 1:1 to Twenty custom objects. Custom object records migrate in the same import order as standard objects, with relation fields created in Twenty before the custom object import step runs.

Entera owner IDs are resolved by email match against Twenty Workspace Members. Before migration runs, all active Entera users must be invited to Twenty and accept their invitations — Twenty's import tool cannot resolve owner relations for users who do not yet exist in the workspace. Unmatched owners are flagged and assigned to a fallback member during migration.

Entera file attachments associated with deals or contacts are preserved in their original location during migration. Files are re-uploaded to the relevant Twenty record as attachments. FlitStack records the original attachment URL in a custom field on the Twenty record for traceability. Entera does not have a native file hosting API, so manual file re-upload is assisted by FlitStack.