Migrate from EXACT to Freshsales

Exact has no native sales pipeline — deal records lack standard pipeline and stage fields

Exact's deal or sales-document records do not include a pipeline or stage field as standard attributes. Freshsales Opportunities require a StageName from a pick-list tied to a specific pipeline. FlitStack creates a default Freshsales Sales Pipeline with standard stages (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost) and maps Exact deal records into it using a value-mapping you define for each document status that represents a deal stage. If Exact tracks deal progress in a custom field, FlitStack uses that field as the stage source. Teams with multiple distinct sales processes will need to define multiple Freshsales pipelines before migration.

Exact API enforces concurrent request limits that constrain bulk migration throughput

Exact Online API throttles concurrent requests per account, requiring FlitStack to use reduced batch sizes when exporting data. Export jobs with more than 50,000 records must be chunked across multiple API sessions with back-off handling between requests. Freshsales' API accepts these chunks at its own rate limit of approximately 100 requests per minute. FlitStack manages both constraints — exporting from Exact in 200-record batches and loading into Freshsales in 50-record batches — and retries transient failures automatically. Very large Exact datasets (500k+ records) require scheduling the export phase during off-peak hours to avoid hitting Exact's concurrent session limits.

Exact custom fields do not auto-create in Freshsales — each requires explicit field creation and type mapping

Exact allows custom fields on contacts, companies, and documents. Freshsales stores custom fields on each object separately — a custom field on an Exact Contact does not automatically exist on a Freshsales Lead or Contact. FlitStack inventories every Exact custom field before migration, creates the corresponding custom fields in Freshsales using the Admin Settings API, and matches data types: Exact text fields create Freshsales text fields, Exact pick-list fields create Freshsales dropdown fields, and Exact date fields create Freshsales date fields. The Freshsales admin must have permission to create custom fields in the target account — Enterprise plan or admin role required.

Freshsales lifecycle stages are single-valued per contact — Exact contact status histories do not carry forward as stage-transition logs

Freshsales Contact Lifecycle Stages (Subscriber, Lead, MQL, SQL, Customer, Evangelist) are single-valued fields — each contact has one current stage. Exact contacts may have a history of status changes recorded across multiple fields or in a log table. FlitStack captures the most recent Exact contact status as the lifecycle stage value in Freshsales, preserving the final status value but not the transition history as a timeline. If your team requires stage-transition history for reporting, FlitStack can write each transition as a custom datetime field (e.g., Stage_MQL_Date__c) using Exact's status-change timestamps.

Exact projects have no native Freshsales equivalent — project data must be manually reconstructed

Exact stores project records with tasks, milestones, and time entries. Freshsales is a CRM and does not include a native project management module. Project records from Exact do not map to any Freshsales standard object. FlitStack flags Exact project records as non-migratable by default and offers two reconstruction paths: either re-create project data as Freshsales Opportunities with custom project-reference fields, or export project data as a CSV for import into a dedicated project management tool alongside Freshsales. Your team decides which path before migration begins.