Migrate from Tall Emu CRM to Salesforce Sales Cloud

Tall Emu Companies map directly to Salesforce Account. The company name, address, phone, email, and website fields are standard field pairs that migrate without transformation. Tall Emu's primary export is Excel from the Companies grid view. We import Accounts first, before any child records, so that the Account ID is available for Contact and Opportunity lookups. If the Tall Emu Company has a custom Company Type or Industry field, we map it to Account Type or Industry (or a custom picklist field if the value is Tall Emu-specific).

Tall Emu Contact records map to Salesforce Contact, linked to the parent Account via AccountId. We export Contacts from the Tall Emu grid after Accounts, resolve the Account lookup by company name match, and set AccountId during the transform phase. Role, title, phone, email, and address fields migrate directly. Any Tall Emu custom fields on Contact pre-require equivalent custom fields in Salesforce, which we create before the Contact import phase begins.

Tall Emu Products carry rich inventory attributes — SKU, description, pricing tiers, stock on hand, serial number tracking, BOM structures, landed cost, and reorder points — that require careful mapping. Standard fields (Name, ProductCode from SKU, Description) map to Salesforce Product2. Stock on hand, reorder points, and BOM component relationships require custom fields or custom objects because Salesforce Sales Cloud does not include native inventory management at the base tier. Serial number tracking may require a custom serial number field on Product2 or a linked custom object. Landed cost is Tall Emu-specific and maps to a custom field in Salesforce.

Tall Emu Pipelines with custom Kanban stages map to Salesforce Opportunity with Record Type and Sales Process configuration. Each Tall Emu pipeline becomes a Salesforce Record Type; the stage names and probabilities map to StageName and StageProbability on the corresponding Sales Process. We configure the destination Record Type and Sales Process before migration so that the correct StageName values are available at import time. Closed-Lost and Closed-Won outcomes from Tall Emu map to Salesforce Opportunity Stage values.

Tall Emu Quotes map to Salesforce Quote (a standard object available from Professional tier). Quote line items map to QuoteLineItem. Quote status (Draft, Sent, Accepted, Declined) requires value mapping to Salesforce QuoteStatus. PDF attachments and document template styling do not migrate; we export filename metadata and flag for manual re-attachment. Quote acceptance status and terms migrate as custom fields if the destination Quote object does not have equivalent fields.

Tall Emu Sales Orders generated from accepted Quotes map to Salesforce Order. Order line items map to OrderItem. Tall Emu Order records carry Product, Quantity, and Pricing references that we resolve to Salesforce Pricebook2 and Product2 IDs during the transform phase. Fulfilment tracking is Tall Emu-specific; we map it to a custom field on Order or a related custom object. Order status values require value mapping to Salesforce Status.

Tall Emu Subscriptions have mandatory fields (Plan, Status, Order Quantity, Billable Quantity, Price, Period, Renewal Due Date) that require a mapping decision based on the destination Salesforce edition. In Professional and Enterprise without Subscription Management, we map Subscriptions to Opportunity records with custom fields (Plan__c, SubscriptionStatus__c, BillableQuantity__c, RenewalDate__c, Period__c) to preserve the data. In Salesforce editions with Paytient Subscription Management (Enterprise+), we map directly to the native Subscription object. Status values (Active, Expired, Cancelled) require explicit mapping to the destination's status vocabulary.

Tall Emu Activities — calls, emails, meetings, and tasks — export from the Activity grid view. We map call engagements to Salesforce Task with TaskSubtype=Call and CallDisposition; email engagements to Salesforce EmailMessage linked to a Task; meetings to Event with StartDateTime, EndDateTime, and Location preserved; tasks to Task with Status, Priority, and ActivityDate. Assignee resolution maps Tall Emu owner email to Salesforce User ID via the User mapping created during discovery. Activity timeline ordering is preserved by setting ActivityDate to the original Tall Emu timestamp.

Tall Emu Freight and shipping records (carrier, tracking number, delivery status) are Tall Emu-specific with no direct Salesforce equivalent. We map freight records to a custom Shipping__c object with lookup to Order, or as custom fields on the Salesforce Order object (Carrier__c, TrackingNumber__c, DeliveryStatus__c). The mapping decision is made during scoping based on the customer's freight workflow complexity.

Tall Emu custom fields on supported modules (Companies, Contacts, Products, Deals) migrate to equivalent Salesforce custom fields. We audit custom field availability per Tall Emu module during discovery before mapping. If a Tall Emu custom field has no Salesforce equivalent, we create a text or picklist field and flag it for manual review after migration. Fields on modules that do not support Tall Emu custom fields require manual field creation in Salesforce before import.

Tall Emu Users map to Salesforce Users by email match. Active and inactive status maps directly. Role and team assignments from Tall Emu map to Salesforce Role hierarchy and Public Group membership. Users are validated against the destination Salesforce org before any record migration begins because OwnerId references on Account, Contact, and Opportunity require a valid Salesforce User ID.

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 (filename, linked record, file type) as a CSV inventory. The customer manually uploads files in Salesforce after migration, using the metadata inventory as a guide. This is a known limitation of Tall Emu's export architecture and is flagged clearly in the scoping document.