Migrate from Anthill CRM to Pipedrive

Anthill Enquiries map directly to Pipedrive Deals. The key transformation is extracting the active workflow stream's stage definitions and mapping them to Pipedrive pipeline stages before import. We generate a workflow-to-pipeline mapping document during scoping that defines which Anthill stream states become which Pipedrive stage names and probability percentages. The Anthill Enquiry ID is preserved in a custom Pipedrive field anthill_enquiry_id__c for cross-reference. Closed Enquiry statuses (won/lost) map to Pipedrive's stage-level won and lost flags.

Anthill Customer records split into Pipedrive Organisation (company data) and Person Contact (individual contact data). Company name and address fields map to Organisation; first name, last name, email, and phone map to the Person Contact linked to that Organisation. We use Organisation ID resolution before inserting Contacts to satisfy the parent lookup. Duplicate Customers sharing the same company name are merged into a single Organisation with multiple Person records.

Anthill's Workflow streams (which define deal progression through state transitions across Sales, Admin, and Support teams) map to Pipedrive Pipelines. Each distinct Anthill workflow stream becomes a Pipedrive Pipeline with stage columns named and ordered to match the original workflow state sequence. Stage probability percentages are computed from the workflow's historical win/loss distribution and set on each stage. Team-level allocation flags in Anthill workflows (Sales, Admin, Support) are preserved as custom fields on the Pipedrive Deal rather than as separate entities.

Anthill Activities tied to Enquiries and Customers map to Pipedrive Activity records (call, meeting, task, note). We preserve activity type, timestamp, and content. Note-type activities migrate as Pipedrive notes with their original timestamps; call and meeting activities preserve duration and disposition where present. Anthill does not expose a documented bulk-export endpoint for activities, so we pull activity records via the JSON API with conservative pagination and validate record counts against any CSV exports available at the object level.

Anthill supports custom fields per object but does not publish a field reference catalogue. We pull the actual field inventory by introspecting the API responses during discovery. Each custom property found is individually mapped: text fields to Pipedrive text fields, picklists to Pipedrive drop-down options, date fields to Pipedrive date fields, and numeric fields to Pipedrive numeric fields. Fields with no matching Pipedrive type are flagged for the customer to decide whether to carry them forward or archive. Picklist option values are cross-referenced against the destination's available options during mapping.

Anthill Users and their team associations (Sales, Admin, Support) map to Pipedrive Users. We resolve Anthill users by email address against the destination Pipedrive account. Anthill does not expose a dedicated user-list endpoint, so we extract user references from Enquiry and Customer owner fields during discovery. Any Anthill user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Anthill automations trigger notifications and email/SMS sequences based on workflow state transitions. Because automations are workflow-scoped and reference Anthill-specific contact properties, they cannot migrate as executable code to Pipedrive. We deliver a written automation inventory that lists each Anthill automation's trigger (state transition), conditions, and actions, with a recommended Pipedrive Workflow equivalent and the steps to configure it. The customer's Pipedrive admin rebuilds the automations post-migration based on this document.

Anthill dashboards are interactive configuration files tied to the platform's internal visualisation engine and are not exposed through the SOAP or JSON APIs. We cannot export them as data. We perform a live dashboard audit during discovery, documenting each dashboard's layout, charts, filters, data sources, and refresh logic from the live Anthill system. This document is handed to the customer so the admin can rebuild the most critical dashboards in Pipedrive's reporting module. For the most important dashboards, we can provide a written specification as a professional services add-on.

Anthill workflow stream state transitions carry deal stage history. When migrating to Pipedrive's column-based pipeline, we capture each state transition timestamp and map it to a Pipedrive Activity record of type note, prefixed with the original workflow state name. This preserves the historical stage progression as a visible audit trail on the Pipedrive Deal, accessible to sales reps who need to understand how a deal moved through the original Anthill workflow.

Anthill assigns workflow actions to Sales, Admin, and Support teams at the record level. In Pipedrive, we replicate this by adding a custom Pipedrive field team_type__c (picklist: Sales, Admin, Support) to the Deal and populating it from the Anthill workflow assignment. Pipedrive's Teams feature (Advanced+ tier) provides a grouping mechanism for users, which we configure to match the customer's Anthill team structure as closely as the destination tier allows.