Migrate from HaystackCRM to Microsoft Dynamics 365 Sales

HaystackCRM Contacts map to Microsoft Dynamics 365 Sales Lead for unqualified prospects and Contact for qualified buyers, mirroring the standard CRM lead-to-contact conversion model. We use HaystackCRM's tag assignments and Opportunity associations as signals: Contacts linked to closed-won Opportunities become Dynamics 365 Contacts; Contacts with no linked Opportunities and no qualifying tag become Leads. The original Haystack Contact ID is stored in a custom field hs_original_id__c on both Lead and Contact for audit and cross-reference. Contact-to-Account linking follows the standard Dynamics 365 relationship after the Account migration completes.

HaystackCRM Company records map directly to Microsoft Dynamics 365 Sales Account. The Company name becomes Account Name, industry and website migrate to standard fields, and address data maps to Address composite fields. We export Companies first and create them in Dynamics 365 before Contacts to satisfy the AccountId lookup requirement on Contact. HaystackCRM Company IDs are preserved in a custom hs_original_company_id__c field for cross-reference during reconciliation.

HaystackCRM Opportunities map directly to Microsoft Dynamics 365 Sales Opportunity with AccountId and ContactId lookups resolved from the Company and Contact migrations. The pipeline stage name migrates as-is but requires pre-configuration of the matching Stage value in the Microsoft Dynamics 365 Sales Process. Temperature priority (Hot/Warm/Cold) from HaystackCRM maps to a custom Opportunity field hs_temperature__c as a picklist since Dynamics 365 does not have a native temperature concept. Closed-Lost and Closed-Won reasons migrate to custom fields or the standard Close field if the destination schema is configured.

HaystackCRM Tasks map to Microsoft Dynamics 365 Sales Task. Status, Priority, and Due Date migrate directly. Owner assignment resolves by email matching against the Dynamics 365 User table. Tasks linked to a specific Contact or Opportunity in HaystackCRM carry a WhatId (Opportunity reference) or WhoId (Contact reference) that we resolve using the reconstructed hs_original_id__c cross-reference created during the primary object migration. Standalone Tasks with no parent link migrate as-is with no WhatId.

HaystackCRM Events map to Microsoft Dynamics 365 Sales Event. Start Time, End Time, Subject, Location, and Description migrate directly. Attendee associations from HaystackCRM do not map to EventRelation records because Haystack's attendee export is limited; we document which Events had attendee lists for the customer's admin to re-invite post-migration. Calendar sync links cannot be reconstructed in Dynamics 365 and must be rebuilt manually in Outlook or the Dynamics 365 mobile app.

HaystackCRM Item/Catalog records map to Microsoft Dynamics 365 Sales Product2. Item name becomes Product Name, SKU becomes Product Code, and list price maps to Standard Price. Product2 records are created before Opportunity Line Item migration so that PricebookEntry lookups resolve at import time. If the customer uses Item variants or sub-items, each variant maps as a separate Product2 record with a parent product relationship if configured in Dynamics 365.

HaystackCRM's flat tag model maps to Dynamics 365 multi-select picklist fields on the relevant entity. We create a custom hs_tags__c multi-select picklist field on Contact, Lead, Account, and Opportunity and populate it with the Haystack tag values. Tags used for segmentation (Who Near Me territory tags, for example) are preserved as-is but customers should note that Dynamics 365 has no equivalent GPS-based proximity feature; territory-based routing requires Dynamics 365 Field Service territory configuration post-migration.

HaystackCRM Teams represent role-based groupings and region assignments. Microsoft Dynamics 365 Sales Team membership maps to the native Team entity, and individual team member roles map to Security Roles within the Team. We export the team roster and role assignments, but Dynamics 365 security roles have a richer permission model than Haystack's grouping — the customer's admin defines which Dynamics 365 roles correspond to which Haystack team roles during pre-migration configuration. Quota and territory assignments do not migrate and require manual reconfiguration in Dynamics 365.