Migrate from Anthill CRM to Microsoft Dynamics 365 Sales

Anthill Enquiries are the primary intake object with no separate Lead concept. We qualify each Enquiry at migration time: those representing early-stage prospects map to Microsoft Dynamics 365 Sales Lead; those with an associated quote, assigned owner, and advanced stage status map to Opportunity. We preserve the original Anthill Enquiry identifier in a custom field (anthill_enquiry_id__c) on both Lead and Opportunity, and carry the Enquiry source channel (e.g. web, phone, referral) into a custom Lead field for attribution reporting.

Anthill Customer records holding core contact and company data map 1:1 to Microsoft Dynamics 365 Sales Account. Standard fields (name, email, phone, address) migrate directly. Anthill's SOAP and JSON APIs expose Create, View, and Modify operations on Customer; we read via the JSON API and write via Dynamics 365 Dataverse Web API. Any custom fields on Customer are individually mapped via the field inventory extracted during discovery, with unmapped fields flagged for the customer to decide whether to carry forward or archive.

Activities tied to Anthill Enquiries and Customers represent touchpoints across the customer journey and map to Microsoft Dynamics 365 Sales Task and Event records. We preserve timestamps, content, and owner assignments. Anthill does not expose a documented activity-history bulk export endpoint, so we extract activities record-by-record via the JSON API, which affects the migration timeline for accounts with large engagement volumes. Activity type (call, email, meeting, note) maps to the corresponding Dynamics 365 activity subtype.

Anthill organises records by team (Sales, Admin, Support) and assigns owners to Enquiries and Customers. We map Anthill Users directly to Dynamics 365 Users and preserve team membership. Anthill does not expose a dedicated user-list API endpoint, so we extract owner references from every Enquiry and Customer record during discovery and build the user inventory from those references. Owner matching in Dynamics 365 is by email; unresolved owners enter a reconciliation queue for the customer's admin to provision before record import.

Anthill supports custom fields per object but does not publish a field reference or schema catalogue. We introspect the actual field inventory by reading API responses during discovery and map each custom property to a typed Dynamics 365 field (text, integer, decimal, picklist, boolean, date). Picklist values are cross-referenced against the destination options. Fields with no suitable Dynamics 365 equivalent are flagged in the mapping document for the customer to decide whether to carry forward as a custom field or archive the data.

Anthill Automations trigger personalised notifications and email or SMS sequences based on workflow state transitions. Because automations are workflow-scoped and reference Anthill-specific contact properties, they do not migrate as code to Dynamics 365. We deliver a written automation inventory documenting each automation's trigger, conditions, actions, and recommended Dynamics 365 Workflow or Power Automate equivalent. Note that Microsoft Dynamics 365 Sales does not include native SMS capability; SMS automations require a separate Power Automate connector or third-party SMS integration licensed by the customer.

Anthill represents deal progression through workflow stream states rather than column-based pipeline stages. We extract each workflow's stage definitions and their associated team assignments during scoping, then map them to Microsoft Dynamics 365 Sales Process stage values. Each Anthill workflow stream becomes a separate Microsoft Dynamics 365 Sales Process or Record Type so that stage values remain scoped per line of business. We preserve the original Anthill workflow state name in a custom field on the Opportunity for audit trail and historical reporting.

Anthill workflows allocate actions to Sales, Admin, and Support teams and track performance via role-based dashboards. We map this team-level allocation to Dynamics 365 Teams and Security Roles. Dashboard configurations themselves cannot be exported via API and do not migrate; we document the layout, metrics, filters, and data sources of the most critical Anthill dashboards during discovery so the customer can rebuild them as Dynamics 365 dashboards or Power BI reports post-migration.