Migrate from Grow CRM to Freshsales

Grow CRM Contacts map directly to Freshsales Contacts. Standard fields (name, email, phone, address, tags) transfer via CSV import using email as the dedupe key. Grow CRM's client custom fields (name, type, options) are extracted from the database during scoping and pre-created as Freshsales custom fields on Contact before import. Any Grow CRM contact that was also linked as a client for invoicing carries a client_type__c custom field in Freshsales to preserve billing context.

Grow CRM Company records map to Freshsales Accounts. The company name becomes the Account Name, and domain or website fields map from Grow CRM's company_url property. Contacts linked to a Company in Grow CRM are imported after the Account exists so that the Contact-Account relationship is preserved at import time through the Freshsales account_id field.

Grow CRM Leads map directly to Freshsales Leads with status, source, and owner preserved. Lead score from Grow CRM transfers to a custom field lead_score__c on the Freshsales Lead since Freshsales's native scoring (Freddy AI) is computed post-migration from new behavioral data. We use email as the unique identifier during import to detect and flag duplicate Leads.

Grow CRM Opportunities map to Freshsales Deals. Deal value, stage, expected close date, and owner transfer directly. Grow CRM pipeline stages are mapped to Freshsales deal stages during import; the stage probability from Grow CRM is stored in a custom field original_probability__c in Freshsales for reference. Closed-won and closed-lost reason fields map to Freshsales deal loss_reason and notes fields.

Freshsales has no native invoice object. Grow CRM Invoices (including line items, totals, tax, payment status, and related client contact) are exported as CSV and converted to PDF or CSV files attached to the corresponding Freshsales Contact or Deal record via Freshsales's file attachment API. Payment status (paid, pending, overdue) is stored in a custom picklist field invoice_status__c on the Contact. Historical paid invoices migrate as closed records; open invoices migrate as open with original due dates preserved.

Grow CRM Estimates (quotes with line items, totals, validity dates, and status) have no direct Freshsales equivalent. We export Estimates as PDF or CSV and attach them to the related Freshsales Deal via the Freshsales file API. The estimate total and validity expiry date are stored in custom fields estimate_total__c and estimate_valid_until__c on the Deal so that sales reps can reference them without opening the attachment.

Grow CRM Payments (amount, gateway Stripe or PayPal, date, linked invoice) are not a standard Freshsales object. We create a custom Payments module from Freshsales Pro plan (custom module) or, for Growth plan migrations, store payment records as Contact activity notes with a structured template: [Payment] Amount: $X | Gateway: Stripe | Date: YYYY-MM-DD | Status: Received. The customer selects the approach during scoping based on their Freshsales plan tier.

Freshsales has no native help desk or case management module beyond Freshdesk (a separate Freshworks product). Grow CRM Help Desk Tickets (status, priority, assignee, conversation history) are exported and conversation threads are preserved as plain-text notes attached to the corresponding Freshsales Contact. Ticket status and priority are stored in custom fields ticket_status__c and ticket_priority__c on the Contact. We document the ticket list in a CSV handoff report so the customer can decide whether to migrate tickets to Freshdesk separately.

Grow CRM tags on Contacts, Companies, and Opportunities are stored as comma-separated values in the CSV export. We normalize tag values during the transform step, recreate the tag taxonomy in Freshsales, and apply tags to the migrated Contact, Account, and Deal records. Tag collisions (identical names on different objects) are resolved by namespace-prefixing: crm_tag, account_tag, deal_tag.

Grow CRM team member roles and permission sets are not structurally exportable. We extract the user list (name, email, assigned role) from the Grow CRM database or user management UI and provide a CSV of team members with their roles. The customer provisions corresponding Freshsales Users manually or through admin import. Role definitions are not migrated; Freshsales's standard profile and permission set model is applied post-migration by the customer's admin.