Migrate from Anthill CRM to Freshsales

Anthill Enquiries are the primary intake object, created via the JSON API endpoint /api/v2/enquiries and automatically triggering the associated workflow. We migrate Enquiries to Freshsales Leads, mapping the Enquiry reference number to the Lead's external_id field and preserving the original creation timestamp. Any Enquiry status or workflow-association fields map to custom Lead fields for audit. If the Enquiry has a linked Customer record, we route the Lead to Contact conversion post-migration based on the customer's status.

Anthill Customer records hold both contact details and company data in one object, which is a common legacy CRM pattern. We split each Customer into a Freshsales Account (the company data) and a Contact (the contact fields), establishing the lookup relationship before import. Contact name, email, phone, and address map directly; the company name maps to Account Name. We use the Customer's unique identifier as the external_id on both records for traceability.

Anthill represents deal progression through workflow stream states, not a column-based pipeline. We extract every distinct workflow stream definition during scoping, list the stage names and their sequence, and generate a workflow-to-pipeline mapping document. Each stream maps to a Freshsales Deal pipeline stage, and the stage order is preserved. Closed-won and closed-lost states from Anthill map to Freshsales Deal statuses with the original workflow exit reason stored as a custom field.

Activities tied to Enquiries and Customers represent touchpoints across the customer journey. We preserve activity timestamps, content, and type (call, email, meeting, task) and map them to Freshsales' activity timeline. Note that Anthill does not expose a documented activity-history bulk-export endpoint, so we use per-record API pulls with staggered pagination. Any missing activity records are flagged in the migration report for the customer to review.

Anthill supports custom fields per object but does not publish a field reference or schema catalogue. During discovery we pull a field inventory by introspecting API responses and map each custom property to its Freshsales equivalent. Picklist values are cross-referenced against Freshsales' allowed values; picklists with values not supported in Freshsales are flagged for the customer to decide whether to carry them forward as text fields or archive them.

Anthill organises actions by team (Sales, Admin, Support) and assigns owners to records. We map Users and their team associations to Freshsales User records, resolving by email match. Team assignments are stored in a custom user field or Territory in Freshsales depending on the customer's intended workflow structure. Anthill does not expose a dedicated user-list endpoint, so we extract user references from Enquiry and Customer owner_id fields.

Anthill Workflows define every customer interaction process with team-level assignments and state-based triggers. Because workflows are configuration-heavy and reference Anthill-specific properties, we do not migrate them as code. We document every active workflow's trigger conditions, stage sequence, team assignments, and automation actions in a written inventory for the customer's admin to rebuild in Freshsales' automation builder. The workflow-to-pipeline stage mapping generated during object mapping serves as the reference for this rebuild.

Anthill's live, interactive role-based dashboards are configuration files tied to the platform's internal visualisation engine and cannot be exported via API. We document the layout, metrics, filters, and data sources from the live system during a dedicated dashboard audit pass. The customer receives a written dashboard specification that maps each Anthill dashboard panel to a Freshsales report or custom dashboard component. Rebuild is a manual admin task or a separate professional services engagement.