Migrate from Eagle CRM to Twenty CRM

Direct 1:1 mapping. Eagle's Contact object maps to Twenty's People object. All standard contact fields (name, email, phone, job title, address) transfer directly. Multi-address support is preserved as the primary address on People. Custom fields on Eagle Contacts map to custom fields on Twenty People. Eagle Contact-Company links resolve via People.companyId after Companies land in Twenty first, ensuring referential integrity.

Direct 1:1 mapping. Eagle's Company object maps to Twenty's Company object. Domain, industry, employee count, annual revenue, address, and social links migrate as direct field mappings. Parent-company hierarchies map to Twenty's parent Company via parentId relationship. We validate domain uniqueness during import to prevent duplicate Company records. Custom fields on Eagle Companies map to custom fields on Twenty Company.

Direct 1:1 mapping. Eagle Deals become Twenty Opportunities. Deal name, amount, expected close date, owner, and associated contacts transfer. Pipeline stage values map to Twenty Opportunity stage pick-list values — we apply value-by-value mapping since Twenty stages are user-configured in the view settings.

Eagle deal pipelines map to Twenty Opportunity stages. Each pipeline in Eagle becomes a named stage option in Twenty's Opportunity stage pick-list. We preserve stage probability percentages as a custom field on Opportunity if your Eagle setup uses probability per stage, since Twenty's default model does not enforce probability.

Direct 1:1 mapping. Eagle Notes migrate to Twenty Notes with the same title, body content, author attribution, and creation timestamps. Notes attached to People, Companies, or Opportunities carry forward their relationship links as Twenty's note-target associations. Rich text formatting in Eagle Notes is preserved in Twenty's Note body field. Notes without attachments migrate as standalone Notes in Twenty's workspace.

Direct 1:1 mapping. Eagle Tasks migrate to Twenty Tasks with title, due date, status, assignee, priority, and linked record references. Open tasks and completed tasks both transfer — completed status renders as completed checkbox in Twenty's Task view. Recurring tasks are flagged as custom fields in Twenty since the native recurrence model differs between platforms.

Eagle activity records (calls, emails, meetings) split into Twenty Tasks and Notes. Call logs with disposition and duration become Tasks with a call-type label. Email threads become Notes with body content. Meeting records with attendees and outcome become Tasks linked to the relevant People or Opportunity.

Eagle custom fields on any object create corresponding custom fields in Twenty on the mapped object. Field type mapping: Eagle text → Twenty text, Eagle number → Twenty number, Eagle date → Twenty date, Eagle pick-list → Twenty select. We surface the full list of Eagle custom properties before migration so Twenty fields can be pre-created in the workspace.

Eagle user records and deal owners resolve to Twenty Workspace Members by email address match. Unmatched owners receive a fallback assignment to a designated migration user and are flagged for admin review. Email is the unique identifier for user resolution on both platforms.

Eagle file attachments download and re-upload to Twenty's file storage. File name, size, and uploader attribution are preserved. Links on records update to Twenty's file URLs post-migration. Large files (>25MB per Twenty's single-file limit) are flagged for manual review before re-upload.

Eagle workflows and automations do not transfer to Twenty. We export the full workflow definition as a structured JSON reference covering trigger conditions, action steps, and field update rules. Your Twenty admin uses this export to rebuild equivalent logic in Twenty's workflow builder, which supports field updates, CRM record creation, and assignee actions.

Eagle sequences (email cadences, follow-up steps) are not migratable. The sequence definitions export as a step-by-step JSON object covering step type, delay, template reference, and exit criteria. Twenty's workflow builder can approximate time-based follow-up sequences using delay actions and CRM update triggers.