Migrate from CASH to Freshsales

CASH contact records map directly to Freshsales Contact objects. Email address is the primary identifier used for deduplication. Freshsales requires that the parent Account be created first when the contact has an associated company — we migrate accounts before contacts to resolve the foreign key.

CASH leads migrate as Freshsales Lead records. Freshsales maintains separate Lead and Contact objects; leads that convert during the CASH usage period retain their lead status in Freshsales as historical records unless a lead-to-contact conversion event is present in the source data.

CASH company records map directly to Freshsales Account objects. Company name, domain, industry, employee count, and annual revenue transfer as Account fields. Parent-company hierarchies in CASH map to Freshsales Parent Account relationships; we resolve circular references before committing the import.

CASH deal records map to Freshsales Deal objects with deal name, amount, expected close date, and owner preserved. Freshsales Deal requires a pipeline assignment; we set the pipeline ID during migration based on the CASH pipeline identifier. Deal probability maps from CASH stage probabilities to Freshsales stage probabilities per pipeline.

CASH pipelines map to Freshsales Pipelines. On Freshsales Growth, only one pipeline is permitted per account — multi-pipeline CASH setups require either merging into one pipeline or upgrading to Freshsales Pro or Enterprise before migration. Stage names and order transfer as Freshsales stage values within each pipeline.

CASH stage names and their display order map to Freshsales Stage values on the corresponding pipeline. Each CASH stage probability becomes the Freshsales stage probability value. If CASH uses custom stage names not present in Freshsales' default stage list, we create custom stage values via the Freshsales pipeline API before loading deal records.

CASH call, email, and meeting records migrate as Freshsales Sales Activities linked to the parent Contact or Deal record. Original subject line, owner, start/end time, and duration are preserved. Freshsales Sales Activities appear in the contact and deal timeline views.

CASH notes migrate as Freshsales Note records attached to the Contact, Account, or Deal. Note body text and any rich-text formatting transfers as-is. If CASH stores notes in a separate attachments table, we link them to the parent object by record ID matching during the import sequence.

CASH users map to Freshsales users by email address match. Unmatched owners receive a fallback assignment to a designated Freshsales admin user and are flagged in the migration report for manual reassignment. Freshsales user roles and profiles must be configured separately post-migration.

CASH custom fields on any object become Freshsales Custom Fields on the corresponding module. Freshsales requires custom fields to be created via the API before data loads — we create field definitions first (with correct data types: text, number, picklist, date, checkbox), then load values. Picklist custom fields use value mapping where CASH picklist values differ from Freshsales defaults.

CASH workflow definitions do not transfer to Freshsales. FlitStack exports workflow rules as JSON for each CASH workflow trigger/action chain. Your Freshsales admin rebuilds these in Freshsales' Workflow Designer (basic on Growth; advanced on Pro/Enterprise). We also document which workflows reference deleted records or inactive users for cleanup.

CASH file attachments on contacts, companies, or deals migrate to Freshsales Files attached to the corresponding record. Files over 25MB cannot be imported via Freshsales API and are flagged for manual re-upload. We preserve the original file name and download URL from CASH for reference.