Migrate from OplaCRM to Freshsales

OplaCRM Accounts map directly to Freshsales Accounts. We match by account name as the dedupe key and map address fields to Freshsales' compound address fields. Any industry or territory data stored in OplaCRM custom fields migrates to Freshsales custom fields on the Account object. OplaCRM's external_id maps to Freshsales' external_id if present for cross-system reconciliation.

OplaCRM Contacts map to Freshsales Contacts by email as the unique identifier for deduplication. Name, phone, and role fields map directly. The contact-to-account link resolves via the account external_id or name match against the Freshsales Account created in the preceding phase. Role information that does not fit Freshsales' standard contact fields migrates to a custom_text field.

OplaCRM Opportunities map to Freshsales Deals. The sale_process_stage field maps by display label to Freshsales stage names rather than by internal enum to prevent a closed-won opportunity landing in the wrong stage bucket. Close date, close reason, and win/loss status migrate to Freshsales standard deal fields. Amount migrates to the Freshsales deal_amount field.

OplaCRM Products map to Freshsales Products with product name and SKU preserved. Pricing may require review if OplaCRM stores list price in a currency-denominated field that Freshsales expects in a different price book model. We map directly and surface any pricing misalignment in the pre-flight reconciliation report.

OplaCRM Invoices created via CreateOpportunityInvoiceDto do not have a direct Freshsales equivalent because Freshsales does not include a native invoicing module in all tiers. We map invoice amount, date, and status as custom fields on the associated Freshsales Deal, and we surface the invoice numbering scheme in the pre-flight report for the customer's admin to assign a Freshsales-compatible numbering convention or document in an external billing system.

OplaCRM pipeline stage names stored as string enums in sale_process_stage map to Freshsales deal stage values by display label. We generate a stage mapping table during pre-flight that the customer reviews and approves before migration runs. Any OplaCRM stage without a Freshsales equivalent is created as a new stage in the destination pipeline.

OplaCRM links joint or co-selling opportunities using opportunities_joint_id (a UUID field). Freshsales does not have a native linked-deals concept. We resolve each UUID into an explicit custom_text property on the Freshsales Deal (e.g., linked_deal_joint_id: <UUID>) and surface the joint relationship in a mapping table so the customer's admin can rebuild the connection manually in Freshsales after cutover if needed.

OplaCRM records carrying the locked boolean flag cannot be edited in OplaCRM. We replicate this as a custom_checkbox field (opla_locked: true) on the relevant Freshsales object during import. Freshsales plan permissions determine whether we can set a true restriction; we use the custom property as the fallback and flag it in the post-migration handoff for the admin to apply read-only permissions at the field or record level.

OplaCRM CustomFieldValueDto key-value pairs migrate as Freshsales custom fields on the corresponding object. We prefix any field names that collide with existing Freshsales standard fields using opla_ and surface a mapping table in pre-flight review so the customer can rename or merge before final import. Custom field types (text, number, date, checkbox, dropdown) map to their Freshsales equivalents by inferred type.

OplaCRM tags stored as label arrays on records map to Freshsales Tags. Any comma-delimited tag strings in OplaCRM are split into individual tag entries per Freshsales tag conventions. Tags with no Freshsales equivalent are created as new tags during import.