Migrate your Anthill CRM data

Enquiries are the primary intake object in Anthill, created via the JSON API endpoint /api/v2/enquiries and automatically triggering the associated workflow on creation. We migrate Enquiries 1:1, preserving the enquiry ID returned at creation time and re-establishing workflow-state linkages in the destination.

Customer records hold the core contact and company data. Anthill's SOAP and JSON APIs expose Create, View, and Modify operations. We map standard fields (name, email, phone, address) directly and flag any custom properties for field-level review.

Anthill's Workflows define every customer interaction process and allocate actions to teams. Because workflows are configuration-heavy objects with team-level assignments and state-based triggers, we export the workflow definitions as structured metadata and map each step to the destination's equivalent process object.

Activities tied to Enquiries and Customers represent touchpoints across the journey. We preserve activity timestamps and content but note that Anthill does not expose a documented activity-history bulk endpoint, so migration relies on per-record API pulls or CSV export supplemented with API validation.

Anthill's live, interactive role-based dashboards are configuration files tied to the platform's internal visualisation engine. These cannot be exported as data and are not exposed via the API. We document dashboard structure during scoping and recreate key metrics manually in the destination where feasible.

Automations in Anthill trigger personalised notifications and email/SMS sequences based on workflow state transitions. Because automations are workflow-scoped and reference Anthill-specific contact properties, we map the trigger logic to equivalent automation rules in the destination CRM, noting any property naming differences.

Anthill supports custom fields per object, but the schema is not publicly documented in a reference format. During scoping we pull a field inventory via the API and map each custom property to its destination equivalent, flagging any picklist or data-type mismatches.

Anthill organises actions by team (Sales, Admin, Support) and assigns owners to records. We map Users and their team associations directly. Note that Anthill does not expose a dedicated user-list endpoint in the public API documentation, so user data is collected during scoping.

Unlike conventional column-based pipelines, Anthill represents deal progression through workflow stream states. We extract stage names and statuses from the workflow definitions and map them to the destination's pipeline stages, flagging any stages that have no equivalent.