Migrate from Prophet CRM to Zoho CRM

Prophet Contacts map directly to Zoho CRM Contacts. Prophet's bidirectional Outlook Contact sync must be frozen before extraction to prevent duplicate records from re-syncing post-import; we coordinate this freeze window with the customer's admin. Email addresses and phone numbers export cleanly. Custom fields on Contacts export as part of the standard OData response and map to Zoho CRM custom fields on the Contacts module, with type conversion (date fields, picklists, checkboxes) handled during the transform phase.

Prophet Companies map to Zoho CRM Accounts. Standard fields including industry, address, employee count, and annual revenue export cleanly. Industry classification and employee count ranges from Prophet map to Zoho's Industry picklist and Employee Count number fields with type normalization. Account is created before Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert.

Prophet Opportunities map to Zoho CRM Deals. Deal name, value, expected close date, probability, owner, and pipeline stage export as part of the record. Stage assignments export as stage names and we map each stage to a corresponding Zoho CRM Deal Stage picklist value during layout configuration. We preserve the original probability percentage in a custom field for pipeline forecasting accuracy after migration.

Prophet pipeline stages are configurable per department, meaning stage names can vary across teams within the same organization. We capture the full stage list during scoping, enumerate each distinct stage name and its probability, and configure Zoho CRM Deal Stage picklist values to match the migrated stage names. Probability percentages map to Zoho's Stage Probability field on each stage. If stages vary by department, we document the per-department stage matrix for the customer's admin to configure territory-based stage assignments post-migration.

Prophet email tracking engagements (sent, opened, clicked) map to Zoho CRM Activity records. The original timestamp, subject, contact association, and opportunity linkage export from the OData API. Group email history stored in Prophet maps to Zoho CRM Tasks with type set to Email. We preserve the activity timestamp ordering by setting the Activity Date to the original Prophet timestamp so the timeline reads chronologically post-import.

Prophet Tasks, Appointments, and Call Logs map to Zoho CRM Activities with the appropriate activity type (Task, Event, or Call) set during transform. Call duration and disposition export from Prophet and map to Zoho Activity custom fields if configured. Each activity record retains its link to the associated Contact and Opportunity via Zoho's What Id and Who Id fields.

Prophet supports custom fields on Companies, Contacts, and Opportunities. These custom fields are created per object and can vary by department template, meaning the effective schema can differ across teams. We audit every custom field name, data type, and which departments use which templates during the mandatory scoping audit. We then pre-create the matching custom fields in Zoho CRM before any data import, using Zoho's field type equivalents (text, number, date, picklist, checkbox, currency) and preserving any department-specific field assignments in Zoho CRM's role-based field visibility settings.

Prophet stores file attachments on Companies, Contacts, and Opportunities. We extract attachment metadata and URLs from the OData export and upload files to Zoho CRM via Zoho's file attachment API. Attachments are linked to the parent record (Account, Contact, or Deal) using Zoho's Attachment module relationship. File size limits and attachment count limits follow Zoho CRM tier constraints.

Prophet departments are a first-class concept with custom templates and configurable cross-department read/write access. Department assignments on records and role-based access settings export as part of the data extract. Zoho CRM does not have an equivalent Department object; instead, we map department assignments to Zoho CRM's Territory management or a custom picklist field on each record, and configure Zoho's sharing rules and role-based field visibility to approximate the cross-department access model. The customer reviews and approves the mapping during sandbox validation.

Prophet Owners map to Zoho CRM Users. We resolve owners by email match against the Zoho CRM destination tenant's User table. Any Prophet Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status in Prophet maps to the Zoho User active flag.

Prophet's group email sending and tracking feature stores email history linked to Contacts and Opportunities. We extract the email body, timestamp, recipient list, and tracking data (opens, clicks) as Activity records in Zoho CRM. The original tracking metadata (open count, click count) is preserved in custom fields on the migrated Activity for historical reporting.

Prophet Enterprise tier supports custom department templates with different field sets, page layouts, and access controls per department. Zoho CRM does not have an equivalent department template model. We document each distinct template's field additions and removals during scoping, and the customer decides whether to apply a unified Zoho CRM layout (simplest) or replicate department-specific views using Zoho CRM's Blueprint and conditional fields features post-migration.