Migrate from Anthill CRM to Nutshell

Anthill Enquiries are the primary intake object created via /api/v2/enquiries. We split by qualification status at migration time: Enquiries with a linked Customer record and completed workflow stages map to Nutshell Person (contact). Enquiries with no linked Customer and early workflow stages map to Nutshell Lead. The original Enquiry creation date and source attribution migrate as custom fields for audit and reporting. We resolve the split criteria during scoping based on the customer's workflow stage definitions.

Anthill Customer records hold core contact and company data. Standard fields (name, email, phone, address) map directly to Nutshell Person. Where Anthill stores a company name on the Customer record, we extract it to create a Nutshell Company and link the Person via the Company relationship. The SOAP and JSON APIs expose Create, View, and Modify operations; we use these to pull the full Customer schema during discovery and map each field individually.

Anthill Workflow streams define customer interaction processes with stage-based state transitions. Each stream state maps to a Nutshell pipeline stage. We extract all stream definitions during discovery, identify the final stage as Closed Won and any exit state as Closed Lost, and configure Nutshell pipeline stages accordingly before migration. Any stage with no direct Nutshell equivalent is flagged for the customer to decide whether to map to an existing stage or create a new one in Nutshell.

Anthill Workflow definitions map to Nutshell Pipelines. Each Anthill workflow stream becomes a Nutshell Pipeline with stages derived from the stream states. We map the workflow owner (team assignment) to a specific Nutshell User during owner reconciliation. Multi-stream workflows with conditional branching require decomposition; we document the branching logic in the migration report for the customer to rebuild in Nutshell as separate pipelines or automation rules.

Activities tied to Anthill Enquiries and Customers represent touchpoints across the customer journey. We preserve activity timestamps, type (call, email, meeting, note), and content directly into Nutshell Activities linked to the corresponding Person or Lead. Note that Anthill does not expose a documented activity-history bulk-export endpoint, so we use staggered API pulls and cross-validate against any CSV exports where available.

Anthill organises actions by team (Sales, Admin, Support) and assigns owners to records. We map Users and their team associations to Nutshell User records. Anthill does not expose a dedicated user-list endpoint; we pull the owner list from record attribution during discovery. Owner resolution by email match creates the mapping; any Anthill owner without a matching Nutshell User goes to a reconciliation queue.

Anthill supports custom fields per object but does not publish a schema catalogue. During scoping we pull a field inventory by introspecting API responses and identify each custom property. Picklist values cross-reference against Nutshell's available field types (text, number, date, picklist). Fields with no direct Nutshell equivalent are flagged for the customer to decide whether to carry them forward as text fields or archive them. Nutshell's Help Center documents the supported custom field types for People, Companies, and Leads.

Anthill automations trigger personalised notifications and email/SMS sequences based on workflow state transitions. These are workflow-scoped and reference Anthill-specific contact properties, making direct migration impossible. We deliver a written inventory of every active Anthill automation with its trigger conditions, actions, and a recommended Nutshell automation rule equivalent. The customer's admin rebuilds these in Nutshell using the Automation settings. Email and SMS sequences require separate configuration in Nutshell's built-in email tools or an external marketing tool.