Migrate from Leadforce CRM to Freshsales

Leadforce Leads map directly to Freshsales Contacts. Standard fields (name, email, phone, source, status) transfer as typed fields. Because Leadforce does not separate a Lead from a Contact object, all Leadforce Leads land in Freshsales Contacts without a conversion step. If the customer uses Leadforce's lead-status lifecycle stages, we preserve those values in a custom field on the Freshsales Contact for segmentation and reporting continuity.

Leadforce does not always use a separate Companies object; company data (company name, website, address) may live within Lead records. We extract these fields during CSV preprocessing, deduplicate by domain or company name, and create Freshsales Accounts. The Freshsales Contact then links to the resolved Account via the Account ID lookup. If the customer does have a distinct Companies object in Leadforce, we treat it as a 1:1 Account migration with the same deduplication logic.

Leadforce Deals map to Freshsales Deals with monetary value, stage name, owner, and expected close date preserved. The Leadforce deal stage becomes a Freshsales Deal Stage, and we configure the Freshsales pipeline stages in Admin Settings to match the Leadforce stage names and order before import begins. Custom fields on Leadforce Deals migrate to Freshsales custom fields on the Deal object.

Leadforce pipeline stage names and order are migrated as Freshsales Deal Stage values configured in Admin Settings under the Deals module. We verify stage count compatibility and map probability percentages where available. The customer reviews the stage mapping before migration to ensure the deal pipeline in Freshsales reflects their current sales process.

Leadforce Activities linked to Leads or Deals migrate to Freshsales Activities with timestamps, activity type, owner, and notes preserved. Chronological ordering is maintained by setting the Freshsales activity timestamp to the original Leadforce timestamp. Call duration and disposition data transfer to Freshsales call activity fields. Activities are imported after Contacts and Deals so that the parent record lookup is satisfied at insert time.

Leadforce Notes (free-text records attached to Leads or Deals) migrate to Freshsales Note records linked to the corresponding Contact or Deal via the record ID. Creation timestamp and author attribution are preserved. Notes are imported after the parent Contact or Deal record exists to maintain relationship integrity.

Attachments linked to Leadforce Deals or Leads require separate file extraction from the export package. We extract files, map them to the corresponding Freshsales Contact or Deal record, and re-attach via the Freshsales API or file upload mechanism. File metadata (filename, size, upload date) is preserved where available in the Leadforce export. This step extends timeline when attachment volume exceeds 500 files.

Leadforce Proposals generated from Deals contain line items and pricing. We export proposals as structured data and reconstruct them in Freshsales as either Deal line item values stored in custom fields or as a structured note attached to the Deal. Native Proposal objects in Freshsales are plan-dependent; we confirm availability during discovery and use the available equivalent.

Invoice records linked to Deals in Leadforce contain payment status and line items. We preserve invoice data as Deal-associated financial records in Freshsales, mapping payment status to a custom field on the Deal. Freshsales does not have a standalone Invoice object in the base CRM; we use Deal custom fields to carry invoice number, amount, and payment status.

Leadforce Owner assignments on Leads, Deals, and Activities map to Freshsales Users. We perform owner lookup by email match: each distinct Leadforce owner email is matched against the Freshsales User table. Any Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner lookup must be resolved before Deal import because OwnerId is required on the Deal object.

Leadforce supports custom fields on Leads and Deals. We audit custom field schemas during a guided screen-share session where the customer walks us through creating a new Lead and Deal record and shows all visible fields. We generate a field mapping spreadsheet with source field name, destination field name, data type, and any value transformation required. Custom fields are created in Freshsales Admin Settings before the import phase begins.