Migrate from Tall Emu CRM to Twenty CRM

Tall Emu Company records map to Twenty Company. Standard fields (displayName, domainName, address, phone) migrate directly. We extract via Tall Emu's Excel grid export, resolve the address sub-fields (street, city, state, postal code, country) into Twenty's address compound field, and use the company domain as the Company domainName. Company is imported first to establish the primary lookup anchor for Contacts and Opportunities.

Tall Emu Contact records map to Twenty Person objects. Email, phone, role, and name fields migrate directly. We import Contacts after Company and match them to the parent Company by company name or a provided external reference field. Tall Emu's role field maps to the Person jobTitle field. Note that Twenty's Person object historically has limited standard fields (GitHub issue #13953 notes missing industry-standard fields); we create custom fields for any Tall Emu contact properties that have no Twenty equivalent before import.

Tall Emu Products carry rich inventory attributes (SKU, description, pricing tiers, stock on hand, serial number tracking, BOM structures, landed costs, reorder points) that have no native Twenty equivalent. We split these into a Product custom object (name, SKU, description, pricing) and a separate Inventory custom object (stock on hand, reorder point, serial number, BOM reference). BOM parent-child relationships flatten into a BOM custom object with parent_product and component_product lookup fields. Landed cost and freight attributes map to custom number fields on the Product custom object.

Tall Emu Pipelines map to Twenty Opportunity records. The pipeline name becomes the Opportunity name, and Tall Emu stage names map to Twenty stage values that we configure in the destination workspace before migration. Stage probabilities migrate as custom number fields. Tall Emu's pipeline-level custom fields migrate as Opportunity custom fields.

Tall Emu Subscriptions (Plan, Status, Order Quantity, Billable Quantity, Price, Period, Renewal Due Date) map to a Subscription custom object with fields for plan_name, status, billing_period, renewal_date, quantity, and unit_price. Status values (Active, Expired, Cancelled, etc.) require value mapping to a status picklist defined in Twenty's Data Model before import. The subscription is linked to the parent Company and Person via lookup fields.

Tall Emu Quotes (line items, pricing, terms, acceptance status) map to a Quote custom object. Quote status (Draft, Sent, Accepted, Declined) maps to a status picklist. Line items migrate as related Quote Line Item custom object records. PDF attachments and template styling do not migrate; we export the quote metadata and flag attachments for manual handoff.

Tall Emu Sales Orders link to accepted Quotes and carry line items, quantities, and pricing. They map to an Order custom object with order_number, status, total_amount, and order_date fields. Order line items migrate as related Order Line Item records. Fulfilment tracking (picking, packing, shipping status) maps to custom fields on the Order object. Note that Twenty does not have native order fulfilment tracking; the customer configures this as a workflow using custom object status values post-migration.

Tall Emu Activities (meetings, calls, emails, tasks) with assignees, due dates, and completion status migrate to Twenty Task and Note records. Meeting details migrate as Note records with meeting-specific fields (location, attendees, duration) stored in custom fields. Call records migrate as Note records with call disposition and duration stored as custom fields. Email content migrates as Note records with the email body as the note content and the timestamp preserved. Activity ordering is maintained by setting the Twenty createdAt to the original Tall Emu activity timestamp.

Tall Emu Users (roles, team assignments) export by email. We match Tall Emu owner references on Contact, Company, Opportunity, and Activity records to Twenty WorkspaceMembers by email. Any Tall Emu user without a matching Twenty account goes to a reconciliation queue. Important: Twenty's migration guide requires users to be invited before import so that owner lookups can be resolved; we sequence User provisioning as a pre-import step.

Tall Emu custom fields on Companies, Contacts, Products, Pipelines, and Subscriptions migrate to Twenty custom fields on the equivalent standard or custom object. We audit custom field availability per module during discovery (some Tall Emu modules do not support custom fields). Before any import, we create all destination custom fields in Twenty Settings → Data Model. Any Tall Emu custom fields without a Twenty equivalent are flagged for pre-migration field creation or mapped to a text property with a note for manual review.

Tall Emu Freight and shipping records (carrier, tracking number, delivery status) export as linked records. They map to a Shipment custom object with carrier, tracking_number, status, and estimated_delivery fields. Since Twenty has no native freight management, the customer rebuilds tracking workflows using the custom object status field post-migration. We do not migrate binary tracking document attachments (proof of delivery PDFs); we export filename metadata and flag for manual handoff.