Migrate your Tall Emu CRM data

Tall Emu's primary account-level record. Standard fields (name, address, phone, email) map cleanly. We export via Excel grid or API and import in bulk first to preserve relationship integrity for downstream Contact and Deal linking.

Contact records sit beneath Companies. Name, email, phone, role, and address fields are stable. We import Contacts after Companies and match them to the parent account by company name or a provided external ID to preserve the hierarchy.

Tall Emu Products include rich inventory attributes: SKU, description, pricing tiers, stock on hand, serial number tracking, BOM structures, landed cost, and reorder points. We export all inventory fields and map them to the destination's product or item object, flagging BOM components for manual reconfiguration where the destination lacks a BOM module.

Tall Emu supports multiple named pipelines with customisable Kanban stages. Stage names, probabilities, and order are exported. We map source stages to destination stages during scoping — stages with no clear destination are flagged for manual assignment post-migration.

Quotes include line items, pricing, terms, and acceptance status. PDF attachments and template styling do not migrate. Quote status (Draft, Sent, Accepted, Declined) requires value mapping to the destination's equivalent lifecycle states.

Sales Orders are generated from accepted Quotes and carry forward line items, quantities, and pricing. They link to Products and Contacts. We preserve the order header and line items; fulfilment tracking (packing, shipping status) requires re-establishment in the destination.

Tall Emu Subscriptions have mandatory fields (Plan, Status, Order Quantity, Billable Quantity, Price, Period, Renewal Due Date). Status values (Active, Expired, etc.) differ between platforms and must be mapped explicitly. Start and End dates are preserved as-is.

Activities include meetings, calls, emails, and tasks with assignees, due dates, and completion status. We export the full activity log and import as history records in the destination; assignee mapping relies on email matching to users in the target system.

Custom fields are supported on most modules via drag-and-drop form builder. We export all custom field values alongside standard fields. Mapping requires the destination to have equivalent custom fields created before import; we flag any orphaned custom fields for pre-migration setup.

Tall Emu tracks freight and shipping workflows including carrier, tracking number, and delivery status. These are exported as linked records. The destination may not have an equivalent freight object — we map them to a generic shipment or notes field and flag for review.

Tall Emu Users have roles and team assignments. We export user records and map to the destination's user object by email. Team structures are preserved as groups or teams in the destination where supported.

Tall Emu stores document attachments (PDFs, images) linked to records, but there is no documented bulk export endpoint for binary files. We export file metadata and filenames and flag attachments for manual download or a separate file-transfer step.