Migrate from Captorra to Zoho CRM

Captorra leads map directly to Zoho CRM Leads. Standard fields (name, email, phone, company) transfer as-is. Captorra's lead source field maps to Zoho's Lead Source pick-list. Custom lead properties migrate as Zoho CRM custom fields. Owner assignment resolves by email match to Zoho users; unmatched owners flagged before migration.

Captorra Case maps to Zoho CRM Potential (also called Cases in Zoho's UI). Captorra's case status pick-list values (New Case, Under Review, Qualified, Filed, Settlement, Closed) map value-by-value to Zoho Potential Stage pick-list values. Stage-transition timestamps preserve as custom datetime fields. The Captorra Case Number becomes a custom field on the Potential.

Captorra contacts map directly to Zoho CRM Contacts. Name, email, phone, address, and title fields transfer as-is. Custom contact properties migrate as Zoho CRM custom fields. Contacts without a linked company in Captorra land as Contacts without an Account lookup; Zoho allows this, and you can assign them to a default account or update them post-migration.

Captorra companies map directly to Zoho CRM Accounts. Company name, domain, industry, employee count, and annual revenue fields transfer as-is. Parent-child company hierarchies in Captorra map to Zoho's Parent Account lookup. Multi-contact companies (Captorra allows N:N contact-company relationships) land with the primary contact on the Account, with additional contacts added via the Contact Roles related list.

Captorra's referral tracking module has no native Zoho CRM equivalent. We create a custom Referral_Source__c module during migration setup with fields for source name, referral date, referring contact, and linked Potential. N:N referral relationships (one contact referred by multiple sources) surface as multiple custom module records linked to the contact.

Captorra's case-type field captures legal classification (e.g., Personal Injury, Employment, Family Law). This maps to a Zoho CRM custom pick-list field (Case_Type__c) on the Potential module. The pick-list values are rebuilt from Captorra's configuration. Zoho's pick-list management requires admin access — we deliver a value-map document as part of the migration plan.

Captorra's damages field captures estimated or claimed damages in case records. This maps to a Zoho CRM currency or number field (Damages__c) on the Potential module. Currency formatting from Captorra (which may include a currency symbol) is stripped and stored as a numeric value in Zoho. Any currency-code metadata from Captorra is preserved in a companion text field.

Captorra matter assignments link a contact to a case with assignment details. In Zoho CRM, a Potential's primary contact is set via the Contact Name lookup. Captorra's multi-contact case assignments (where one case has multiple assigned contacts) collapse to a single primary contact per Potential, with additional contacts surfaced through the Contact Roles related list in Zoho.

Captorra tasks and case activity records map to Zoho CRM Tasks. Subject, due date, status, and priority transfer as-is. Task owner resolves by email match to Zoho users. Activity timestamps and descriptions preserve from Captorra. Captorra's custom activity types (e.g., Court Filing, Client Call) map to a custom Activity_Type__c field on the Zoho Task.

Captorra notes and case documents map to Zoho CRM Notes. Note title, body content, and associated record link transfer as-is. Rich-text formatting from Captorra notes may require normalization — we test note rendering in Zoho during the sample migration phase. Original create dates preserve as a custom Created_In_Source__c field.

Captorra file attachments re-upload to Zoho CRM's Attachments module. Each file links to its parent record (Lead, Potential, or Contact). Zoho's file size limit is 25 MB per attachment. Files exceeding this limit are flagged during the audit phase and require either a pre-migration split or external hosting with a URL stored as a custom field on the record.

Captorra user and owner records resolve by email match against Zoho CRM users. Unmatched owners are flagged before migration begins; your team either creates Zoho users for them before the migration run or assigns their records to a fallback Zoho user. Captorra's role-based permissions do not map to Zoho's profile and role model — those are configured separately post-migration.