Migrate from Tall Emu CRM to Microsoft Dynamics 365 Sales

Tall Emu Company records map to Dynamics 365 Account. The company name becomes Account Name, phone and email map to Telephone1 and Website respectively, and address fields map to Address composite fields. Account is imported first in all migration sequences because Contact, Opportunity, and Quote records hold foreign-key Lookups to Account. We use the Tall Emu Company ID as an external key stored in a custom field tallemuid__c on Account for cross-system reconciliation after cutover.

Tall Emu Contact records map to Dynamics 365 Contact. Email, FirstName, LastName, Phone, JobTitle, and Role map directly. The parent AccountId is resolved at import time by matching Tall Emu's Company name or Company ID to the imported Account record. Dynamics 365 requires each Contact to have an AccountId Lookup; Contacts without a resolvable parent Company are held in a reconciliation queue for manual Account assignment before import proceeds.

Tall Emu Products map to Dynamics 365 Product2. Standard fields — Product Name, Product Number (from SKU), Description, Standard Price, and Unit — migrate directly. Inventory attributes (stock on hand, serial number tracking, reorder points, and landed costs) do not have native Microsoft Dynamics 365 Sales equivalents in the Product2 object; these are stored in a custom field tallemu_inventory__c as structured text for admin reference, with the recommendation to enable Business Central for inventory depth if ongoing tracking is required.

Tall Emu Pipeline Deal stages map to Dynamics 365 Opportunity StageName via a configured Sales Process per pipeline. Tall Emu's pipeline count and stage names are preserved: each Tall Emu pipeline becomes a Dynamics 365 Record Type with its own Sales Process whitelisting the relevant stages. Probability percentages migrate to StageProbability with rounding to the nearest integer. Estimated Close Date and Actual Close Date map directly. The parent AccountId and OwnerId are resolved at import time using the previously imported Account and User records.

Tall Emu Quotes map to Dynamics 365 Quote. Quote Number, Name, Account (via Lookup), Description, and Active Date migrate. Quote status (Draft, Sent, Accepted, Declined) requires value mapping to Dynamics 365 StateCode and StatusCode because the enumeration values differ between platforms. Line items migrate to QuoteLineItem with resolved Product2 reference and PricebookEntry. PDF attachments and template styling do not migrate; we export the template metadata and flag it for manual recreation in Dynamics 365.

Tall Emu Sales Orders map to Microsoft Dynamics 365 Sales Order. The order header (order number, date, Account reference, Owner reference) and line items migrate together. Order status mapping follows the same StateCode/StatusCode translation as Quotes. Microsoft Dynamics 365 Sales Order is available in Sales Professional and above. Fulfillment tracking and shipment status from Tall Emu are preserved as structured text in a custom field fulfillment_notes__c on the SalesOrder because Microsoft Dynamics 365 Sales does not include a native shipment tracking object.

Tall Emu Subscriptions carry Plan, Status, Order Quantity, Billable Quantity, Price, Period, and Renewal Due Date — fields with no direct Microsoft Dynamics 365 Sales Professional equivalent. We create a custom Subscription entity in the destination Dataverse environment with matching custom fields, and link it to Account via a Lookup. Alternatively, for simpler billing visibility, we map Renewal Due Date and Plan to custom fields on the Account or to Opportunity records tagged with a Subscription Record Type. The choice is made during scoping based on the customer's reporting needs. Subscription status transitions require admin to update manually post-migration or via Power Automate.

Tall Emu Activity records (calls, emails, meetings, tasks) map to Dynamics 365 Task, EmailMessage, and Event. Calls and tasks become Task records with TaskSubtype set appropriately; emails become EmailMessage records linked to a parent Task for timeline display; meetings become Event records with StartDateTime, EndDateTime, and Location preserved. Assignee is resolved by matching the Tall Emu owner email to the imported User record. ActivityDate ordering is preserved on import. Very large activity histories (over 200,000 records) are chunked via the Bulk API with exponential backoff on rate-limit responses.

Tall Emu custom fields on each module are audited during discovery. We create equivalent custom fields in Dynamics 365 via the maker portal before import. Field type mapping follows: Tall Emu text fields become Text or Note (depending on length), numeric fields become Number or Decimal, date fields become DateTime, and picklist fields become Option Sets. Fields with no matching Tall Emu module support are flagged during scoping. If a destination custom field does not yet exist, we create it first and note it in the pre-migration field creation checklist.

Tall Emu freight records (carrier, tracking number, delivery status) have no native Microsoft Dynamics 365 Sales equivalent. We export freight metadata alongside the Order records and load it into a custom field freight_data__c on the SalesOrder as structured text (carrier, tracking URL, delivery date). Customers requiring live shipment tracking are advised to enable the Dynamics 365 Supply Chain Management or a third-party logistics integration post-migration.

Tall Emu Users are exported by email and matched to Dynamics 365 Users by email address. Role and team membership from Tall Emu are preserved in a custom field tallemu_teams__c and mapped to a Dynamics 365 Team or security role during configuration. Owners without a matching Dynamics 365 User are placed in a reconciliation queue; the customer provisions the missing User before record import continues because OwnerId is a required field on most standard objects.

Tall Emu stores document attachments (PDFs, images) linked to records, but there is no documented bulk export endpoint for binary files. We export attachment metadata — filename, linked record, file type — into a CSV inventory and flag each attachment for manual upload to Dynamics 365 SharePoint or OneDrive via the record's document tray post-migration. The customer reviews and uploads attachments during the hypercare window.