Migrate from Getfly CRM to Freshsales

Getfly Accounts map to Freshsales Contact records with Organization linkage. We assess during scoping whether the customer uses B2B (Account maps to Organization with Contacts) or B2C (Account maps directly to Contact). Email becomes the dedupe key. Standard fields (name, phone, email, address) migrate directly. Custom fields on Getfly Accounts are mapped to Freshsales Contact custom fields or Organization custom fields based on the chosen model.

Getfly Products hold item-level data including pricing, SKU, and custom fields in nested detail_custom_fields. We flatten these into scalar columns compatible with Freshsales Product fields. ProductCode maps from Getfly sku. Active/inactive status migrates as Product status. Products are loaded before Deals so that line-item references resolve at import time.

Getfly deal stages are customer-specific and extracted from the full stage configuration. Each Getfly stage becomes a Freshsales Pipeline stage with name and probability preserved. Stage order migrates to Freshsales stage sequence. If Getfly uses multiple pipelines, each maps to a separate Freshsales Pipeline. The customer confirms stage mapping during scoping before migration begins.

Getfly Activities (type, date, duration, owner assignment, linked account) map to Freshsales Tasks. Activity type maps to Freshsales Task category field. Owner assignment resolves via email-based lookup to Freshsales User. Date and duration migrate directly. Tasks load after Contact and Organization to satisfy parent-record lookups.

Getfly PABX call logs include call direction, duration, and recording URL references. We export these as Freshsales Tasks with a call disposition field. Recording URLs are downloaded to local storage at export time and re-uploaded to Freshsales file storage. If Freshcaller is adopted as the call replacement, call records migrate to Freshcaller Call Logs. URL time-limited links are handled during the export window to prevent broken references.

Getfly Users are exported by name, email, and role. We resolve each Getfly owner email against Freshsales Users by email match. Owners without a matching Freshsales User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status migrates where supported. Role assignments are noted for documentation but do not auto-provision role-based permissions in Freshsales.

Attachments associated with Getfly Accounts or Products are referenced by URL in the API. We download files to local storage during export and re-upload to Freshsales as file attachments linked to the corresponding Contact or Organization record. Original filenames are preserved. File size limits for Freshsales attachment uploads apply and are verified during scoping.

Marketing campaigns in Getfly (name, start/end dates, linked accounts) migrate to Freshsales Target Lists. Campaign membership—indicating which accounts were contacted—migrates as tagged Target List membership. Active campaign status maps to Target List active/inactive. If the customer uses Freshmarketer in parallel, campaign data maps to Freshmarketer Campaigns instead.

Getfly workflow rules are internal platform configuration with no public export endpoint. We do not migrate automations as code. We deliver a written inventory of every active Getfly Workflow with its trigger, conditions, actions, and recommended Freshsales automation equivalent. The customer's admin rebuilds automations in Freshsales using the automation builder. This documentation step is completed during the discovery phase before any data moves.