Migrate from Tall Emu CRM to HighLevel

Tall Emu Company records map to GoHighLevel Contacts with the Company name stored in the Location field or in a custom Company_Name__c contact field. We export Company records first and use the Company name as a dedupe key during Contact import. If the customer uses Tall Emu's company-level addresses or phone numbers separately from Contact addresses, we nest these as Contact custom fields or import them into GoHighLevel's standard Contact address fields. The decision between Location and custom field is made during scoping based on how the customer uses Tall Emu's Company module.

Tall Emu Contact records map directly to GoHighLevel Contact. Email, phone, role, and address fields migrate cleanly. We import Contacts after creating the Location or Company custom field context so that the company relationship is preserved. If a Contact's parent Company is not present in the export, we flag the orphan for manual resolution. GoHighLevel's Contact model does not require a separate Account object, which simplifies the Tall Emu Company-to-Contact mapping.

Tall Emu Products map to GoHighLevel Products for CRM quoting purposes only. Tall Emu's rich inventory attributes (stock on hand, serial number tracking, BOMs, landed costs, reorder points) have no GoHighLevel equivalent and do not migrate. We export the product name, SKU, description, and pricing tiers as GoHighLevel Product records. The customer should configure a separate inventory management tool if serial number or BOM tracking is business-critical. We flag this gap in the scoping document.

Tall Emu Pipelines and Deal records map to GoHighLevel Opportunities. Each Tall Emu pipeline becomes a GoHighLevel Pipeline with custom stages recreated in the destination. Stage names, probabilities, and order migrate. We configure GoHighLevel pipeline stages and stage probabilities during schema setup before Opportunities are imported. Closed-won and closed-lost deal values and dates map to Opportunity fields.

Tall Emu Quotes migrate to GoHighLevel Opportunities with line items, or to GoHighLevel Documents if the customer uses the Documents feature for quote PDFs. Quote status (Draft, Sent, Accepted, Declined) maps to a custom Opportunity status field or tag since GoHighLevel does not have a native quote object outside of Opportunities. PDF attachments and template styling do not migrate; we note the need to rebuild quote templates in GoHighLevel's document builder post-migration.

Tall Emu Orders (generated from accepted Quotes) migrate to GoHighLevel Opportunities with the order header and line items carried as Opportunity Line Items. Order status tracking does not have a GoHighLevel equivalent; we map fulfillment stage to an Opportunity tag or custom field. Customers using Tall Emu's order-to-fulfillment workflow should rebuild order status tracking in GoHighLevel using Opportunities with tags or a custom pipeline stage.

Tall Emu Subscriptions have mandatory fields (Plan, Status, Billable Quantity, Price, Period, Renewal Due Date) that do not have a native GoHighLevel equivalent. We model Subscriptions as Opportunities with custom fields: Plan maps to a custom Plan_Name__c field on Opportunity, Status maps to Opportunity stage or a custom Status__c field, and Renewal Due Date maps to a custom Renewal_Date__c field. The customer decides whether subscriptions live as Opportunities with renewal pipeline stages or as a separate CRM workflow managed through GoHighLevel's workflow automation. We document the mapping and flag this as a configuration decision.

Tall Emu Activities (meetings, calls, emails, tasks with assignees, due dates, and completion status) migrate to GoHighLevel Tasks and Notes attached to the relevant Contact or Opportunity. We export the full activity log including the activity type, timestamp, assignee, and body content. GoHighLevel's activity timeline renders tasks chronologically; historical timestamps are preserved. Assignee resolution uses email matching against GoHighLevel Users. Large activity histories (over 100,000 records) use GoHighLevel's bulk import with chunking.

Tall Emu custom field values migrate to GoHighLevel custom fields, but GoHighLevel requires explicit designation of Contact custom fields versus Opportunity custom fields at creation time, and this cannot be changed after field creation. We audit all Tall Emu custom fields during discovery, determine which object they belong to in GoHighLevel, and recreate them before import. If a Tall Emu custom field applies to both Contacts and Deals, we create it on both objects and note the duplication. Custom field types (text, number, date, dropdown) are mapped to GoHighLevel field types during schema setup.

Tall Emu Users are mapped to GoHighLevel Users by email. We export all Tall Emu user records including roles and team assignments. Team assignments map to GoHighLevel Tags or Groups. Any Tall Emu user without a matching GoHighLevel user email is held in a reconciliation queue for the customer to provision before Contact and Opportunity import resumes.