Migrate from RAYNET CRM to Zoho CRM

RAYNET Contacts with lifecycle stages before 'customer' (subscriber, lead, marketing qualified) map to Zoho CRM Lead. RAYNET Contacts at 'customer' lifecycle stage or beyond map to Zoho CRM Contact attached to a Zoho Account. We compute the split using RAYNET's lifecycle stage field at migration time and preserve the original RAYNET lifecycle value in a custom field raynet_lifecycle__c on both Lead and Contact for audit. The Contact-to-Account relationship is resolved by matching RAYNET's Company field against the Zoho Account name during insert.

RAYNET Account (Company) records map directly to Zoho CRM Account. RAYNET's company name becomes Account Name, billing and shipping addresses migrate to the standard Zoho address fields, and the account website maps to Website. Account is created before any Contact or Deal import so that the lookup relationship is satisfied at the moment of insert.

RAYNET Deals map to Zoho CRM Deals. The RAYNET pipeline stage maps to a Zoho Sales Process that we configure before migration, with stage probabilities preserved as percentages in Zoho Stage Probability fields. Deal owner resolves by email match against Zoho Users. Closed-Lost and Closed-Won statuses migrate as standard Zoho Deal stages with any custom RAYNET loss/win reasons preserved as custom fields.

RAYNET Activity records (Calls, Emails, Meetings) map to Zoho CRM Tasks (for calls and emails) and Events (for meetings). Call duration and disposition migrate to custom Task fields; meeting start and end times map to Event Start Time and End Time. Each Activity is linked to its parent Contact or Account via the Zoho Activity's WhatId and WhoId fields. We resolve parent IDs during migration using cross-reference tables built from the RAYNET export.

Each RAYNET pipeline becomes a Zoho Sales Process with stage names mapped to Zoho stage labels and probabilities. Stage order is preserved from RAYNET's pipeline stage configuration. On RAYNET START tier (single pipeline), we create a single Zoho Sales Process; on RAYNET PROFESSIONAL or ENTERPRISE with multiple pipelines, we create one Zoho Sales Process per RAYNET pipeline and assign the appropriate Record Type to each Deal during migration.

RAYNET Users map to Zoho CRM Users by email match. Active RAYNET users who have no corresponding Zoho User are flagged in a reconciliation queue for the customer's admin to provision before record migration begins. Role assignments and deal ownership migrate as Zoho User roles that the admin assigns post-migration.

RAYNET Sales Order records (Subject, Final Price, Status, Estimated Costs, Delivery Date, Shipping/Billing address) map to Zoho CRM Sales Order. We handle address field splitting and map RAYNET's order status to Zoho's Sales Order status picklist values. Line items require Product2 lookup resolution against Zoho's product catalog.

RAYNET Quotes linked to Deals and Accounts map to Zoho CRM Quotes with validity dates and pricing preserved. Quote line items map to Zoho Quote Items with Product2 reference resolution. Signed Quote PDFs migrate as Zoho Attachments linked to the Quote record via the Zoho file upload API.

RAYNET custom Contact and Account fields are extracted via list export and mapped to Zoho CRM custom fields of equivalent type (text, number, picklist, date, checkbox). Zoho field creation happens before data import. If no equivalent Zoho field exists, we create one and document it in the field mapping sheet. GPS coordinates from RAYNET's Map Analysis are preserved as two Zoho custom number fields (latitude, longitude) if the customer's Zoho admin chooses to maintain geographic data post-migration.

Files attached to RAYNET Contacts, Accounts, Deals, and Activities are exported and re-associated to the correct Zoho records using record ID cross-references built during the export phase. We match by original filename and parent record name. Attachments exceeding Zoho's file size limits are flagged for manual handoff.

RAYNET tags on Contacts and Deals migrate as Zoho Tags (text arrays stored on the record) or as a Zoho multi-select picklist field depending on the customer's Zoho configuration preferences chosen during scoping. The tag label set is preserved verbatim; duplicate labels are deduplicated before import.