Migrate from crmConnect to Zoho CRM

crmConnect Contact records migrate to Zoho CRM Leads. We evaluate each contact's source (inbound form, manual entry, import) and pipeline association to determine whether the record should land as a Zoho Lead or a Zoho Contact attached to an Account. Duplicate contact cards in crmConnect are resolved by matching on email address before migration: the most recently updated record per email address wins, and older duplicates are flagged in a suppression report for the customer admin to review.

crmConnect Pipeline maps to Zoho CRM Pipeline. Stage names, transition rules, and stage ordering migrate directly. If the crmConnect account is on Standard tier with only 1 pipeline and 5 opportunities, we confirm that the target Zoho edition supports the planned pipeline count before migration and flag any opportunity records that would exceed the Standard cap.

crmConnect Opportunities map to Zoho Deals. We preserve deal amount, stage assignment, closing date, owner (resolved by email match to Zoho User), and any linked contact associations. Custom opportunity properties require field-by-field discovery during the export phase because crmConnect exposes no documented API schema endpoint; we map each discovered custom field to a typed Zoho custom field before import.

crmConnect automations use a drag-and-drop builder with no documented export format. We capture automation intent from screenshots and JSON metadata where accessible, document the trigger type (event-based, time-based, field-change), condition logic, and action sequence, and deliver a written inventory recommending equivalent Zoho Workflow Rule configurations. The customer's admin rebuilds automations in Zoho Blueprint or Workflow Rules post-migration.

crmConnect Calendar records with event times, attendees, and linked contact associations migrate to Zoho Events. Standard tier in crmConnect limits to 1 calendar; we verify the total calendar count during scoping and confirm the target Zoho edition supports the equivalent event volume. Google Calendar and Outlook sync settings are source-platform configuration that requires manual re-enablement in Zoho.

crmConnect membership portals and course enrollments are treated as separate record types with status, enrollment dates, and student records. We migrate these as a Zoho Custom Module created during schema design, with membership status mapped to a picklist, enrollment dates mapped to date fields, and student records linked via lookup to the Zoho Contact. The module name and field schema are designed during discovery based on the specific crmConnect data fields present.

Funnels and landing pages in crmConnect are content objects rather than data records. We export funnel structure and page content as template documentation, noting that Zoho Sites or an external landing page tool will need manual reassembly. The content of each funnel stage and page is preserved as a structured file inventory for the customer's marketing team to rebuild.

Email campaign templates and send history export as text and metadata from crmConnect. We preserve template body content and contact association lists. Automation sequences tied to sends (triggers, delays, A/B conditions) are documented separately as workflow metadata because they require rebuild in Zoho as Workflow Rules or email automation sequences. Template HTML may require reformatting to match Zoho's email template syntax.

crmConnect SMS text blast sequences (Professional tier, 3 sequence limit) export as sequence definitions and subscriber lists. We map subscriber lists to Zoho Contacts tagged with SMS opt-in status, and document sequence structure for rebuild in Zoho Workflow Rules with SMS Deluge actions or a connected SMS tool. Sequence step timing and conditional branching are preserved in the automation inventory.

crmConnect Professional tier e-commerce store products (up to 6) migrate to Zoho Products with Standard Price Book entries. We map product name, price, SKU, and contact associations. The Zoho e-commerce or payment integration (Zoho Checkout, Zoho Books) requires separate configuration post-migration; we document the current product list and associations as a setup reference.

Historical invoices export as records with line items and payment status from crmConnect Professional tier. We map line items and payment status to Zoho CRM Invoices or a connected Zoho Books instance, depending on whether the customer licenses Zoho Books separately. Open invoice status migrates as-is; historical paid invoices are preserved as read-only records for audit.

Custom contact and opportunity properties in crmConnect have no documented API schema endpoint. We discover available custom fields during the multi-file export phase by examining each CSV column header, then map them field-by-field to typed Zoho custom fields. Field type mapping accounts for text, number, date, picklist, and boolean equivalents in Zoho's schema. This discovery step adds time to scoping and is the primary driver of the custom object migration cost premium.