Migrate from openCRX to Freshsales

openCRX Contact records (individual persons) map to Freshsales Contact. We extract first name, last name, primary email, phone numbers (via PhoneNumber objects), postal address (via PostalAddress objects), and any DataBinding PropertySet custom fields. The Freshsales Contact is created after its parent Account (from LegalEntity) to satisfy the AccountId lookup at insert time. Segments containing both LegalEntity and Contact records must be processed together to resolve the organisation hierarchy.

openCRX LegalEntity records map to Freshsales Account. We extract company name, website, industry classification, revenue range, and any DataBinding PropertySet custom fields. LegalEntity is the parent of Contact records in openCRX; we use the LegalEntity name as the Account name and the Contact's organisation reference to establish the Freshsales Account-Contact relationship. Multi-entity openCRX deployments with multiple segments require segment-level Account reconciliation before migration.

openCRX Opportunities inherit from abstract contract classes and may contain complex position-level detail (contract positions as line items). We flatten contract positions into a single Deal record, extracting the opportunity name, amount, currency, close date, and rating. Stage names from openCRX map to Freshsales Deal stage values, with the original openCRX stage preserved in a custom field for audit. If multiple openCRX opportunities share a single Contact or LegalEntity, each becomes a separate Freshsales Deal linked to the same parent Account.

openCRX Quotes inherit from the same contract hierarchy as Opportunities and contain line positions modelled as contract positions. For Freshsales Growth and Free plans, we migrate Quote header data (customer reference, currency, total amount) into the parent Deal as a custom field block or note. For Freshsales Pro and Enterprise, Quotes migrate to the native Freshsales Quote module with line items, pricing, and validity dates preserved. Quote-to-Deal linkage is maintained via the parent Account lookup.

openCRX Sales Orders are terminal contract records in the order-to-invoice chain. We map Sales Order headers and positions to Freshsales Deal records, flagging the original openCRX type as a custom field so that won Deals retain their order context. openCRX pricing rules applied at order time are captured as a JSON block in a custom Deal field if they cannot be expressed in Freshsales native pricing. Invoice records follow the same pattern and map as closed-won Deals with invoice status tracked in a custom field.

openCRX products with multi-currency price lists and run-time pricing rules map to Freshsales Product records. We extract product name, SKU (from openCRX productCode), description, and unit price. For products with pricing rules rather than fixed prices, we capture the effective price at migration time as the standard price in Freshsales and document the original pricing rule for the customer's admin to re-implement in Freshsales pricing logic if needed.

openCRX Activities (calls, emails, meetings, tasks) map to Freshsales Task and Event records. Activity time-tracking attributes, disposition codes, and duration migrate to Task custom fields. openCRX Activity Trackers group related activities and are a grouping concept with no Freshsales equivalent; we document tracker-to-record associations in a migration note and set a custom field on each migrated activity indicating its original tracker membership. Custom feature definitions and activity subtypes require field-level mapping during scoping.

Custom fields added via openCRX DataBinding PropertySet are stored as feature definitions bound to CrxObject at runtime. We identify all active custom fields during scoping, map their data types to Freshsales equivalent field types (text, number, date, picklist, checkbox), and pre-create the corresponding custom fields in Freshsales under the correct module before data import. Custom field definitions that reference openCRX-specific picklist values require value mapping as part of the transformation step.

openCRX stores binary attachments linked to objects via WebDAV. If attachments are accessible via openCRX's WebDAV endpoint, we extract them on a Linux or macOS client to avoid Microsoft's WebDAV implementation quirks that cause silent file access failures on Windows. Attachment metadata (filename, MIME type, created date, linked object) is preserved and re-attached to the corresponding migrated record in Freshsales. openCRX groupware document folders that rely on WebDAV-specific access patterns may require manual extraction with customer DBA assistance.

openCRX role-based security with segment-scoped user assignments maps to Freshsales User records. We resolve active users by email address match between openCRX and Freshsales. Any openCRX user without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import. Role and permission mappings (openCRX segment roles to Freshsales profile and permission sets) are documented as a written inventory for the admin to configure post-migration.