Migrate from Origo BPO to Freshsales

Origo BPO client contacts including named customer representatives and service managers map directly to Freshsales Contacts. We preserve the original create dates as a custom field on each Contact record since Freshsales CreatedDate will reflect the migration timestamp rather than the original record creation date. Email, phone, and address fields map one-to-one to their corresponding Freshsales Contact fields. The original create date is preserved in a custom datetime field to maintain the full historical record for audit and reporting purposes.

Origo BPO stores client company names and domains. These map to Freshsales Accounts. The Account Name maps directly; website and industry fields map value-by-value where Origo BPO uses a pick-list. Parent-child company hierarchies in Origo BPO map to Freshsales Parent Account relationships.

Origo BPO service-agreement records (SLA tier, contract value, renewal date) have no direct Freshsales equivalent. We map these to a Freshsales Deal with custom fields: SLA_Tier__c, Contract_Value__c, Renewal_Date__c, and Service_Type__c. Deal Name is derived from the client company plus 'SLA' identifier.

Origo BPO operational stages including Prospecting, Onboarding, Active, At-Risk, and Renewal map to corresponding Freshsales Deal stage values per configured pipeline. We build a dedicated Freshsales pipeline named 'Client Services' to isolate service-agreement deals from any standard sales pipeline activity. This separation ensures service workflows are tracked independently and visible only to teams managing ongoing client relationships rather than new business development.

Origo BPO agents and account managers are resolved by email match to Freshsales Users. Unmatched agents are flagged before migration; you either invite them to Freshsales or assign their records to a fallback Owner. This ensures every Deal and Contact has a valid Freshsales OwnerId.

Origo BPO logs service requests, SLA updates, and client communications as operational notes or linked records. We map these to Freshsales Tasks with Type='Service Activity', preserving the original timestamp, assigned agent, and a link back to the parent Contact or Account via the WhatId field.

Origo BPO contact records with phone numbers map to Freshsales Contact Phone and Mobile Phone fields directly. If Origo BPO stores only a single phone field, we route it to Phone by default and flag the record for manual review of the Mobile Phone field.

Origo BPO internal notes and client communications stored as text fields migrate to Freshsales Notes. We preserve the original author (from the agent name) and creation timestamp. Rich-text formatting in Origo BPO notes is flattened to plain text for compatibility with Freshsales Note objects.

Origo BPO classifies clients by segment (e.g., SMB, Mid-Market, Enterprise) in a custom field. Freshsales has no native account-segment field, so we create Account_Segment__c as a pick-list custom field with Origo BPO's exact segment values preserved.

Origo BPO billing records and invoice histories do not map to any standard Freshsales CRM object. We preserve key invoice data including invoice amounts, payment status, and billing contact as custom fields on the related Deal for reference. This includes Invoice_Amount__c, Payment_Status__c, and a billing contact email custom field. Full invoice history with line items and payment records requires a separate accounting system and is not migrated as part of this process.

Origo BPO internal record IDs are stored as Source_System_ID__c on each Freshsales object including Contact, Account, and Deal for comprehensive traceability. This field enables delta-run deduplication to identify which records have been modified since the initial migration load, supports rollback identification if a partial rollback is required, and provides a cross-reference between the original Origo BPO record and its Freshsales counterpart for audit and reconciliation purposes.