Migrate from Anthill CRM to Salesforce Sales Cloud

Anthill Enquiries are the primary intake object and feed into a workflow stream on creation. We split Enquiries into Salesforce Lead (for early-stage, unqualified records) and Salesforce Opportunity (for Enquiries that have progressed past a defined workflow threshold set during scoping). The split rule uses workflow state names and a status threshold defined in the discovery mapping document. The original Enquiry ID and workflow stream name are preserved in custom fields enq_original_id__c and enq_workflow_stream__c for audit and cross-referencing.

Anthill Customer records hold contact and company data. We map company-level data (company name, address, industry) to Salesforce Account and contact-level data (name, email, phone, role) to Salesforce Contact, linking Contact to Account via AccountId. Anthill's per-customer notes migrate as Salesforce Notes attached to the Contact. If a Customer record has no named contact (e.g. a company-only record), it creates an Account with no associated Contact and is flagged for the customer to decide whether to add a contact owner.

Anthill organizes actions and record assignments by team — Sales, Admin, Support. Salesforce has no direct Team object; we map this to a combination of User records (one per Anthill team member) and either a Salesforce Queue per team (for case and lead routing) or Role hierarchy (for territory-based reporting). The customer chooses the mapping strategy during scoping based on how they use Anthill teams day-to-day. The team association on each record migrates as a custom picklist field team_original__c so that the admin can use it in reports.

Anthill Workflows define every customer interaction process with state-based transitions and team-level action allocations. Because workflows are configuration-heavy, we do not migrate them as code. We extract every unique workflow definition from the Anthill API during discovery, document the state names, transition rules, and team assignments, and use this to configure Salesforce Record Types (one per Anthill workflow) and Sales Processes with stage values that match the workflow states. This is the core structural remap that distinguishes an Anthill-to-Salesforce migration from a simple record copy.

Anthill workflow stream states map to Salesforce Opportunity StageName values. We extract the full list of state names from each workflow definition during discovery, rank them by progression order, and map them to Salesforce Stage entries. Stage probability percentages are assigned based on the original Anthill workflow state's estimated close likelihood, rounded to the nearest integer per Salesforce's constraints. The mapping document generated during scoping is applied before any Opportunity import runs.

Anthill Activities tied to Enquiries and Customers represent touchpoints across the customer journey. We map phone call activities to Salesforce Task with TaskSubtype = Call and CallDurationInSeconds in a custom field. Meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Email activities map to Salesforce EmailMessage (the content) linked to a Task record (the timeline entry). Anthill does not expose a documented activity-history bulk export; we pull activity records via the per-Enquiry API with staggered requests and cross-validate against any CSV export available per object.

Anthill supports custom fields per object but does not publish a field reference catalogue. During discovery we introspect the actual API response payloads to pull the live field inventory for every object. Each custom field found is individually mapped to a Salesforce custom field with the equivalent data type (text, number, date, picklist, checkbox). Picklist values are cross-referenced against Salesforce's allowed values. Fields with no Salesforce equivalent are flagged for the customer to decide whether to carry them forward as a custom field or archive them. API name follows Salesforce convention with __c suffix.

Anthill Automations trigger personalised notifications and email/SMS sequences based on workflow state transitions. Because automations are workflow-scoped and reference Anthill-specific contact properties, they cannot be migrated as code to Salesforce Flow. We deliver a written inventory of every active Anthill Automation with its trigger (workflow state name), conditions, actions (notification type, recipient, message), and a recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds the automations post-migration.

Anthill live, interactive role-based dashboards are configuration files tied to the platform's internal visualisation engine and are not exposed via the SOAP or JSON APIs. We do not migrate dashboards as data. We conduct a dashboard audit during discovery, documenting the layout, widget types, filters, date ranges, and underlying data sources for each Anthill dashboard so the customer's admin can rebuild the most critical ones in Salesforce Reports and Dashboards or Analytics Cloud. For customers requesting full rebuild support, this can be scoped as a separate professional services engagement.

Anthill Users map to Salesforce User records. We resolve Anthill users by email match against the Salesforce destination org's User table. Team associations (Sales, Admin, Support) migrate as a custom picklist field team_role__c. Any Anthill User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Anthill users can be migrated as inactive Salesforce Users to preserve assignment history.

Anthill Enquiry status values (e.g. New, In Progress, Awaiting Response, Closed Won, Closed Lost) map to a combination of Salesforce Lead Status (for records in the Lead object) and Opportunity StageName (for records that have progressed to Opportunity). The mapping table is generated during scoping by inspecting the Anthill workflow state definitions and assigning each state a position in the destination pipeline.

If Anthill is used for quote generation, Quote records migrate to Salesforce Quote, available from the Professional tier in Sales Cloud. Quote PDFs and any attached files migrate as ContentDocument records linked to the Quote via ContentDocumentLink. Quote line items map to OpportunityLineItem once the parent Opportunity is created and a Pricebook2 is assigned.

If Anthill holds product catalogue data, Products migrate to Salesforce Product2 records with Standard Price Book entries created during import. ProductCode, description, and pricing fields migrate directly. A Pricebook2 is assigned before line items are imported so that OpportunityLineItem records have a valid PricebookReference.