Migrate from OplaCRM to Zoho CRM

OplaCRM Accounts map directly to Zoho CRM Accounts. We use the account name as the dedupe key during import and preserve the external_id field as a custom field if present. Address data (street, city, state, postal code, country) maps to Zoho's standard address compound fields. Account healthscore from OplaCRM maps to a numeric custom field Opla_Healthscore__c because Zoho CRM has no native healthscore equivalent.

OplaCRM Contacts map to Zoho CRM Contacts with email as the deduplication key. The contact-to-account link resolves via external_id matching against Zoho Accounts. Role and title fields map to Zoho's standard Contact fields. Custom Field values (CustomFieldValueDto key-value pairs) write to Zoho custom fields, prefixed with opla_ if naming collisions occur with existing Zoho fields.

OplaCRM Opportunities map to Zoho CRM Deals. The sale_process_stage string enum maps to Zoho CRM Deal Stage by display label matching rather than internal enum ordinal to ensure CLOSE_WON and CLOSE_LOST land in the correct terminal stage. Close date, close reason, and win/loss status migrate to Zoho's Closing Date, Reason for Lost, and Stage fields. External_id preserves for update matching.

Each distinct OplaCRM pipeline stage string value creates a corresponding Zoho CRM Deal Stage in the customer's Sales Process configuration. Stage probability percentages migrate to Zoho's Stage Probability values. Multiple OplaCRM pipelines map to separate Zoho Sales Processes or Record Types if the destination tier supports it.

OplaCRM Products map to Zoho CRM Products with product name and SKU preserved. Pricing may require review if OplaCRM stores list price differently from Zoho's price book model. We create Standard Price Book entries during migration to satisfy the price book reference on Deal line items.

OplaCRM Invoices created via CreateOpportunityInvoiceDto map to Zoho CRM Invoices with invoice amount, date, and status. Invoice numbering schemes between systems require explicit remapping during scoping; we flag the numbering gap and document the chosen scheme for the customer's admin to confirm.

OplaCRM uses the opportunities_joint_id UUID field to link joint or co-selling opportunities. We resolve each UUID into an explicit linked-opportunity relationship. In Zoho CRM Enterprise/Ultimate, Linked Deals provides a native mechanism; in Standard/Professional tiers, we create a custom lookup field Joint_Opportunity__c referencing the related Deal and write the joint connection explicitly. UUIDs that cannot resolve to a matching OplaCRM Opportunity are surfaced in the handoff document for manual review.

OplaCRM's locked boolean flag prevents edits on the source. We replicate the restriction by creating a custom field Opla_Locked__c on each migrated module and setting it to true for locked records. Zoho CRM does not have native record-level locking, so the customer's admin reviews locked records post-migration and applies Zoho CRM field-level security or permission set restrictions manually. We flag every locked record in the pre-flight review.

OplaCRM Custom Field values stored as CustomFieldValueDto key-value pairs migrate to Zoho CRM custom fields. We pre-create the Zoho custom fields during schema setup, prefixed with opla_ when names collide with existing Zoho properties. The mapping table surfaces in pre-flight review so the customer can rename, merge, or drop colliding fields before final cutover.

OplaCRM tags stored as label arrays on records map to Zoho CRM Tags. Comma-delimited tag strings in OplaCRM split into individual tag entries during import. Zoho CRM Tags apply across modules, matching OplaCRM's cross-record tag behavior.

OplaCRM Users map to Zoho CRM Users by email address match. Owner assignments on Accounts, Contacts, and Deals resolve to Zoho CRM OwnerId at migration time. Any OplaCRM Owner without a matching Zoho User enters a reconciliation queue for the customer's admin to provision before record import resumes.

OplaCRM file attachments referenced by URL or file ID are downloaded and re-uploaded to Zoho CRM attachment storage. Large binary attachments may require extended migration windows and are flagged in the pre-flight report. We attempt direct URL download where OplaCRM exposes attachment URLs; file-ID-based attachments require API access confirmation during discovery.