Migrate from Grow CRM to Zoho CRM

Grow CRM Contacts map directly to Zoho CRM Contacts. Standard fields (name, email, phone, address, tags) migrate as typed Zoho fields. Grow CRM's client custom fields (any fields beyond the standard set) require pre-creation in Zoho before import; we extract the field definitions from Grow CRM's database or UI during scoping and create matching custom fields in Zoho's Contacts module first.

Grow CRM Company records map to Zoho CRM Accounts. The company name becomes the Account Name, domain information maps to the Website field, and the contact-to-company relationship is preserved as a Zoho Account-Contact lookup. We resolve the Account record before Contact import so that the Parent Account and Account Name lookups are satisfied at insert time.

Grow CRM Leads map to Zoho CRM Leads. Lead status, source, and owner assignment migrate to Zoho's Lead Status, Lead Source, and Owner fields respectively. Grow CRM's lead custom fields are handled the same way as Contact custom fields: definitions extracted during scoping, pre-created in Zoho before import.

Grow CRM Opportunities map to Zoho CRM Deals. Deal name, value, stage, expected close date, and owner migrate directly. Grow CRM's pipeline and stage definitions map to Zoho's Pipeline and Stage picklist values. Stage history (pipeline movement timestamps) is not natively stored in Grow CRM and cannot be reconstructed in Zoho without manual records.

Grow CRM allows custom fields on Clients and Tasks. These field definitions are not included in the standard CSV export. We extract field definitions (name, data type, picklist options) from the Grow CRM database or UI during scoping and document them as a schema specification. We pre-create matching custom fields in Zoho CRM before any record import. Custom fields are not available in Zoho CRM's Free edition; if the destination is Free tier, we flag this as a scope constraint.

Grow CRM Invoices map to Zoho CRM Invoices if the destination includes the Zoho CRM Invoices module (Professional and above). Invoice line items, totals, tax, payment status, and the client contact link migrate. Historical paid invoices migrate as closed records; open invoices require a Zoho Books integration if the customer needs accounts-receivable workflow management. Grow CRM's Stripe and PayPal payment gateway references do not migrate as active payment connections.

Grow CRM Payment records (amount, gateway, date, linked invoice) map to Zoho CRM Payment records linked to the corresponding Invoice. Payment gateway references (Stripe, PayPal) are stored as text fields in Grow CRM; these migrate as read-only text fields in Zoho. Active payment gateway connections must be reconfigured in Zoho Payments or reconnected to Zoho Books.

Grow CRM Estimates (proposals or quotes) with line items, totals, validity dates, and status map to Zoho CRM Quotes. Quote validity dates migrate to the Zoho Quote Valid Till field. Signed or accepted estimates can be flagged with a custom Status field to indicate original acceptance state.

Grow CRM Help Desk Tickets map to Zoho CRM Cases. Ticket status, priority, assignee, and conversation history migrate. Conversation threads in Grow CRM export as plain text; we preserve them as Case Description or as linked Notes attached to the Case. Ticket pipeline stages map to Case Status values in Zoho.

Grow CRM Knowledge Base articles (title, content, category, publish status) export as HTML or markdown. We map them to Zoho CRM Knowledge Base articles under the corresponding category structure. Grow CRM's flat article structure is recreated with Zoho's category hierarchy. Articles with draft status migrate as unpublished in Zoho.

Tags on Contacts, Companies, and Opportunities in Grow CRM are stored as comma-separated values or arrays. We normalize tag values during extraction and recreate the tag taxonomy in Zoho CRM using Zoho's Tag feature. Tag mapping is handled as a post-import cleanup step if the destination Zoho instance uses a different tagging convention than Grow CRM.

Grow CRM role definitions (team member access control settings) are not structurally exportable. We extract the user list, their assigned roles, and permission levels from the database during scoping. We document the role matrix as a specification for Zoho's Profiles and Roles configuration, which the customer or a Zoho partner rebuilds post-migration. Active Salesforce-style permissions are not migrated automatically.