Migrate from Grow CRM to Salesforce Sales Cloud

Grow CRM Contacts map to either Salesforce Lead or Contact depending on lifecycle role. Contacts flagged as prospects with no associated Opportunity map to Salesforce Lead. Contacts with active deals or invoicing history map to Salesforce Contact tied to an Account. We preserve Grow CRM contact tags as a multi-select picklist field and store the original Grow CRM contact ID in a custom field gco_id__c for cross-system reference.

Grow CRM Company records map directly to Salesforce Account. The Company phone, address, website, and industry fields map to the corresponding Account fields. Account is created before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Grow CRM's company-contact relationship is preserved via AccountId on Contact.

Grow CRM's standalone Lead records (distinct from Contacts) map directly to Salesforce Lead. Lead status, source, and owner assignment transfer to the corresponding Salesforce Lead fields. We resolve Grow CRM owner email to Salesforce UserId and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before production migration.

Grow CRM Opportunities map to Salesforce Opportunity. Deal value, stage name, expected close date, and owner assignment transfer. Stage mapping is explicit per pipeline since Grow CRM pipeline names vary. We configure Salesforce Record Types and Sales Processes for each Grow CRM pipeline before migration so that Opportunity stages are valid on insert. Closed-Lost and Closed-Won dates migrate from Grow CRM's stage history timestamps.

Grow CRM Tasks map to Salesforce Task. Grow CRM custom fields on Tasks require pre-creation in Salesforce before migration; we extract the field definitions (name, type, picklist options) from the Grow CRM database during scoping and create matching custom fields with a gco_ prefix. Task assignment resolves Grow CRM owner email to Salesforce OwnerId. Completed tasks preserve their status and ActivityDate from the source timestamp.

Salesforce Sales Cloud has no native invoice object. Grow CRM invoices (line items, totals, tax, status, and client link) migrate as a custom Invoice__c object we create during schema design, with InvoiceLineItem__c as a related custom object. PDF copies of historical paid invoices migrate as ContentDocument records attached to the corresponding Account. Open invoices are migrated as records with their full detail so the customer can re-issue in Salesforce or a connected billing tool.

Grow CRM Payments (amount, gateway Stripe or PayPal, date, linked invoice) migrate as a custom Payment__c object with a lookup to the Invoice__c record. Payment gateway reference migrates as a text field. We do not reconnect Stripe or PayPal during migration; the customer re-links payment processing to their chosen tool post-migration.

Grow CRM Estimates (line items, totals, validity dates, status) migrate to Salesforce Quote if the destination org has Quotes enabled, or to a custom Estimate__c object if not. Estimated-to-Invoice conversion status is preserved as a custom status field since Quote acceptance does not auto-create an Invoice in Salesforce. Valid historical Estimates that were accepted become Closed Won; expired Estimates become Closed Lost.

Grow CRM Help Desk Tickets map to Salesforce Case. Ticket status becomes Case Status, priority becomes Case Priority, and assignee maps to Case OwnerId. Grow CRM conversation threads export as plain text and migrate to EmailMessage records linked to the Case, preserving the customer-facing thread history. For teams using Salesforce Service Cloud, Case Origin maps from the Grow CRM ticket channel field.

Grow CRM role definitions are not structurally exportable. We extract the user list, their assigned roles, and permission scopes from the database and document them as a role matrix. The customer's Salesforce admin uses this matrix to assign Profiles and Permission Set Groups to users post-migration. We do not migrate Grow CRM roles as code.

Grow CRM tags on Contacts, Companies, and Opportunities are stored as comma-separated values in the database. We extract all distinct tag values, normalize them, and recreate them as Salesforce custom multi-select picklist fields on the corresponding objects. The customer chooses per-object tag strategy during scoping.

Grow CRM custom fields on Clients and Tasks are not included in the standard CSV export. We extract field definitions (field name, data type, picklist values) directly from the Grow CRM database during scoping and use them to pre-create matching custom fields in Salesforce. The schema specification document is reviewed and signed off before any data migration begins. Without this step, custom field data is silently dropped during standard CSV import.