Migrate your Grow CRM data

Grow CRM's primary person record. We export all standard contact fields (name, email, phone, address, tags) and preserve them as a flat contact record. Email-to-contact linking for the client portal is maintained during migration.

Company records store business details and link to multiple Contacts. We preserve the contact-to-company relationship by mapping the foreign key at import time. Companies import cleanly with standard fields.

Grow CRM tracks leads separately from Opportunities. We preserve lead status, source, and assignment fields. Leads are imported as a distinct object and can be merged or linked to Opportunities in the destination CRM.

Opportunities track deal value, stage, expected close date, and owner assignment. We map pipeline stages explicitly since naming conventions vary between CRMs. Stage history is not natively preserved in Grow CRM exports.

Tasks support custom fields in Grow CRM, and task assignments link to team members. We extract all custom field definitions from the source instance and map them to equivalent destination fields, recreating the extended schema in the target.

Invoices include line items, totals, tax, status, and a link to the client Contact. We export full invoice records including payment status. Historical paid invoices are migrated as closed records; open invoices are flagged for follow-up in the new system.

Payments record amounts, gateways (Stripe or PayPal), and dates tied to invoices. Grow CRM stores payment history as related records. We map Payments to the corresponding invoice or contact in the destination, handling gateway references as informational only.

Estimates (proposals or quotes) include line items, totals, validity dates, and status. We migrate Estimates as standalone objects where the destination supports them, or convert them to Invoices if the target CRM does not have a separate Estimates object.

Tickets track customer support queries with status, priority, assignee, and conversation history. Conversation threads may be exported as plain text, which we preserve as a Notes or Activity record in the destination CRM.

KB articles include title, content, category, and publish status. We export articles as HTML or markdown and map them to KB categories in the destination. Grow CRM's article structure is flat; we recreate the category hierarchy.

Client portal access records and login activity are not exported via Grow CRM's standard export tools. Portal access credentials cannot be migrated. We document which contacts had portal access so the customer can re-invite clients post-migration.

Grow CRM supports team member roles with access control. Role definitions are not structurally exportable. We extract the user list, their assigned roles, and recreate role configurations in the destination using equivalent permission sets.

Contacts, Companies, and Opportunities can be tagged. Tags are stored as comma-separated or array values. We normalize tag values during import and recreate the tag taxonomy in the destination CRM.

Grow CRM allows custom fields on Clients and Tasks. The custom field schema must be manually defined in the destination before import. We extract field definitions (name, type, options) from Grow CRM and recreate them as matching fields in the target platform.