Migrate from Tall Emu CRM to Nutshell

Tall Emu Companies map directly to Nutshell Organizations. Name, address (street, city, state, postcode, country), phone, website, and industry fields migrate cleanly via Excel export. We use Organization name as the dedupe key during Import2 ingestion and ensure Organizations are imported before any Contact import so that the Organization-Person link is satisfied at the moment of insert.

Tall Emu Contacts map to Nutshell People. First name, last name, email, phone, role (title), and address fields migrate directly. We import People after Organizations and match each Person to its parent Organization by company name or a pre-provided cross-reference. Role and department are stored as text fields in Nutshell People since Nutshell does not have a dedicated department object.

Tall Emu's named pipelines with custom Kanban stages require pre-migration stage design in Nutshell. Nutshell uses a single pipeline per account with configurable stage names and probabilities. We extract all Tall Emu pipeline names and stage names during discovery, propose a Nutshell stage configuration that preserves the original sales logic, and configure it before any Deal import begins. Multiple Tall Emu pipelines are merged into one Nutshell pipeline unless the customer requests a workaround using Nutshell's account types as a soft segmentation.

Tall Emu Opportunities map to Nutshell Deals. Deal name, amount, stage (mapped via the Stage configuration above), close date, probability, and owner all migrate directly. The Tall Emu pipeline assignment maps to the Nutshell Stage configuration. Closed-won and closed-lost reasons stored as custom properties in Tall Emu migrate to text fields in Nutshell Deals.

Tall Emu Activities (calls, emails, meetings, tasks) with assignees, due dates, completion status, and body text migrate to Nutshell Activities. Activity type is preserved as the Activity type field in Nutshell. Assignee resolution uses email matching to the Nutshell user table. We import Activities after People and Deals so that the Person and Deal links are established at insert time.

Tall Emu Products migrate to Nutshell Products with SKU, name, description, and price migrating directly. Tall Emu's inventory attributes (stock on hand, reorder point, serial number, BOM structure, landed cost) have no equivalent in Nutshell Products and are flagged for pre-migration decision: the customer either drops them, stores them in custom fields (if Nutshell plan supports enough), or documents them for a separate inventory management tool. We export all product data from Tall Emu's Excel export including any inventory columns visible in the grid view.

Tall Emu Quotes include line items, pricing, terms, and acceptance status (Draft, Sent, Accepted, Declined). Nutshell Deals support line items but do not have a standalone quote object. We map accepted Quotes to Deal line items with status preserved as a custom field. PDF attachments and quote template styling do not migrate. Quote status values require explicit value mapping during Import2 configuration.

Tall Emu Subscriptions (Plan, Status, Order Quantity, Billable Quantity, Price, Period, Renewal Due Date) have no direct Nutshell equivalent. We map Plan and Status to custom fields on the Person record (for individual subscriptions) or on a Deal (for account-level recurring billing). The customer selects the preferred strategy during scoping. Renewal Due Date migrates as a date field. This mapping requires the destination Nutshell plan to support the required number of custom fields.

Tall Emu custom fields on Companies, Contacts, Opportunities, and Products migrate to Nutshell custom fields of equivalent type (text, number, date, dropdown). Nutshell plan determines the maximum number of custom fields. We audit Tall Emu custom field availability per module during discovery — some Tall Emu modules do not support custom fields and we flag any gaps before migration. Custom fields on modules without a Nutshell equivalent (Subscriptions, Freight) are mapped to the nearest available target object.

Tall Emu Users with roles and team assignments map to Nutshell Users. We export user records by email as the matching key. Team structures in Tall Emu are mapped to Nutshell groups or remain as a documented reference for the customer's admin to reconfigure in Nutshell Settings. Any Tall Emu user without a matching Nutshell account goes to a reconciliation queue for the admin to provision before record import.