Migrate from Opal CRM to Freshsales

Opal CRM Leads map to Freshsales Contacts because Opal uses a single Lead object without a separate Contact concept. We preserve the lead source attribution, any custom fields discovered during scoping, and the assigned Sales Rep owner by resolving the owner email to a Freshsales User record. If the customer needs to retain unqualified prospects as Leads in Freshsales, we configure a Lead status field and map the source accordingly during scoping.

Opal CRM team members with Admin, Manager, or Sales Rep roles map to Freshsales User records. Role permissions do not export as structured data from Opal CRM, so we capture role assignments per user during discovery and document the mapping so the Freshsales admin can reconfigure equivalent access tiers (Full, Limited, or Read-Only) post-migration. Active users are mapped first; inactive users are created as deactivated records to preserve historical assignment references.

Opal CRM Tour Plans store itinerary data (dates, locations, route sequence) and expense line items (amount, category, description). Freshsales has no native Tour or Visit object. We create a custom Tour Plans module in Freshsales with fields for itinerary_date, location, route_order, and expense entries, or attach structured notes if the Growth plan custom module limit is a constraint. We decompress any flat export rows containing both itinerary and expense data and reconstruct them as individual structured records. If the export collapses Tour Plan expense data into a notes field, we flag each affected record for manual review.

Opal CRM Quotations map to Freshsales Quote records with line items. The quotation header fields (quotation number, date, total amount, currency) migrate directly. The internal approval workflow state is a platform-specific concept in Opal CRM that has no standard Freshsales equivalent, so we capture the last workflow status value and store it in a custom field quotation_workflow_state__c. The Freshsales admin rebuilds any approval routing logic using Freshsales Workflows if the Garden plan or above is subscribed.

Opal CRM tracks lead progress through implied pipeline stages. Stage names and order migrate to Freshsales Deal stages. Each stage maps to a Freshsales Deal Stage value, and the stage probability percentages are configured in the Deal Stage setup. If the customer has multiple Opal CRM pipelines, we create corresponding Freshsales Deal stages grouped by pipeline name.

Opal CRM engagement logs (calls, emails, meetings) attached to Leads migrate to Freshsales Call Logs (for calls), Tasks (for emails and standalone tasks), and Events (for meetings). We set the activity date to the original Opal CRM timestamp to preserve timeline ordering. If the export delivers activity history as a flat notes field rather than structured rows, we parse timestamps and restore them as individual activity records, flagging any records with ambiguous dates for manual review.

Opal CRM supports custom fields on Leads and possibly other objects, but the schema is not publicly documented. We identify custom fields during discovery by reviewing the customer's manual export output and map them to Freshsales custom fields of equivalent type (text, number, date, picklist). We use Freshsales' custom field UI (available from Growth tier) to provision the destination fields before migration begins. Any custom properties with unsupported data types are stored as text fields and flagged in the handover notes.

Opal CRM role definitions (Admin, Manager, Sales Rep) do not export as structured data. We capture the role assignment per user during discovery and document the mapping to Freshsales access tiers (Full Access, Limited Access, Read Only). The Freshsales admin assigns roles post-migration based on this documented mapping. This is a manual configuration step, not a data migration step.