Migrate from OrangeCRM to Freshsales

OrangeCRM Customer is the primary account-level object with embedded contact and fulfillment data. We extract the account-level fields (company name, domain, address, custom account properties), create the corresponding Freshsales Account, and preserve any OrangeCRM-specific account fields as custom fields on the Account object. The Customer record's unique identifier is stored for subsequent child-record resolution.

Contacts export from OrangeCRM's Customer module with standard fields (name, email, phone, address). We map these 1:1 to Freshsales Contacts and handle multi-value phone or email fields by splitting into separate field values. The parent Customer ID is used to link each Contact to the resolved Account in Freshsales after the Account import phase completes.

Fulfillment records track subscription or order fulfillment status tied to Customers. This is a proprietary OrangeCRM concept with no direct Freshsales equivalent. We create custom fields on the Freshsales Deal object to carry fulfillment status, fulfillment date, and any subscription-specific metadata. The original fulfillment-stage values are preserved as picklist values in the custom field. Parent Customer resolution ensures the Deal links to the correct Account.

OrangeCRM Help Desk tickets store status, priority, assignee, and conversation history. We map these to Freshsales Case records, with OrangeCRM ticket status mapped to Freshsales Case status values and priority mapped to Case Priority. Conversation threads are converted to Case Thread records or Note attachments on the Case. The linked Customer record resolves to the Account in Freshsales.

Email campaign subscriber lists and opt-in status in OrangeCRM map to Freshsales Contacts with custom fields capturing subscriber opt-in dates, campaign engagement metrics, and list membership. We preserve the original list structure as a contact property rather than migrating to Freshsales Lists (which is a separate sales engagement concept). Email consent flags map to Freshsales contact email preference fields.

OrangeCRM BI reports and dashboards are configuration data, not transactional records. We export report definitions as JSON metadata and deliver them as a written reference document. The actual analytics data does not migrate because it is derived from the underlying records which are already in Freshsales. Rebuilding reports in Freshsales' analytics module is handled by the customer's admin post-migration.

Storefront orders and product records in OrangeCRM map to Freshsales Deals with Products and Line Items. Order totals, line item descriptions, quantities, and fulfillment status transfer to Deal fields and related Deal Line Items. Any proprietary OrangeCRM product IDs are preserved in a custom field on the Product record for audit. This split is required because OrangeCRM conflates order and product in one module.

Some OrangeCRM deployments include a Banking module for payment or ledger tracking. This has no Freshsales standard equivalent. We map to Freshsales Deals with custom fields capturing payment amount, currency, transaction type, and any ledger reference. Currency handling is flagged during scoping if multi-currency records are present; Freshsales Currency field type accommodates this.

Event registrations and attendee records map to Freshsales Event records with attendee status and session selections preserved as custom Event fields. Each registrant also links to the corresponding Freshsales Contact record. Custom event metadata (track, session, ticket type) migrates as custom fields on the Event object.

OrangeCRM custom fields per module are extracted via the export pass. We generate corresponding Freshsales custom fields with type-matched field types (text, number, date, picklist, multi-select) before any data import begins. The full custom field schema is validated against the OrangeCRM export to ensure no fields are missed during extraction.

File attachments on OrangeCRM records export as URL references or binary blobs depending on the export method available. We preserve the attachment URL where OrangeCRM provides it, or download and re-upload to Freshsales. In either case, the attachment is linked to the resolved parent record in Freshsales (Account, Contact, Deal, or Case) via the standard attachment relationship.

OrangeCRM user accounts and record owners map to Freshsales Users. We perform an owner lookup during import by matching email addresses. Any OrangeCRM Owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records is updated once the User resolution completes.