Migrate from Origo BPO to Salesforce Sales Cloud

Origo BPO client organizations map directly to Salesforce Accounts. Company name, domain, industry, and address fields transfer to the corresponding Account fields. Multi-location clients may require parent Account setup in Salesforce to preserve the hierarchical structure of the organization within the CRM.

Client contacts from Origo BPO map to Salesforce Contacts with an AccountId lookup. The primary contact per client attaches directly to the Account record; additional contacts attach via Account Contact Relations for N:N relationships. Service role fields migrate as custom pick-list fields on the Contact object.

Origo BPO service engagements with defined contract values map to Salesforce Opportunities. Engagement name becomes Opportunity Name; engagement start and end dates map to CloseDate or custom date fields. Stage and probability derive from engagement status at migration time, preserving the current state.

Service engagements tracked for delivery, SLA compliance, or support purposes without a revenue value map to Salesforce Cases. The engagement ID is stored as Source_System_Engagement_ID__c on the Case record for full traceability back to the original Origo BPO record. Case status maps directly from engagement status values.

Origo BPO staffing assignments (worker-to-client mappings with role and date ranges) have no direct Salesforce standard equivalent. We migrate these to a custom Staffing_Assignment__c object with lookups to Account for the client, Contact for the worker, and the related engagement. Assignment status, role, and date ranges map to custom fields.

Origo BPO activity logs including calls, emails, meetings, and notes migrate to Salesforce Tasks and Events. Original timestamps and owner assignments are preserved during the transfer. Activity type determines Task Subject or Event Type. The parent record link attaches the activity to the corresponding Account or Contact in Salesforce.

Origo BPO KPIs such as utilization rates, SLA scores, and satisfaction ratings have no Salesforce standard equivalent. These migrate to a custom Performance_Metric__c object with lookup to Account and date fields for recording period. Metric type and value are stored as custom fields; your team defines the reporting structure in Salesforce after migration.

Origo BPO custom fields on client records map to Salesforce custom fields with the __c suffix. Before migration, FlitStack generates a schema setup plan so your Salesforce admin creates required fields. Field types including text, picklist, number, and date map according to source data format and Salesforce field type constraints.

Origo BPO workers assigned to engagements resolve by email match against Salesforce Users. Matched workers become the OwnerId on Task and custom object records. Unmatched workers are flagged in a pre-migration report — your team either invites them to Salesforce or assigns their records to a designated fallback user.

Origo BPO file attachments on client records and engagements re-upload to Salesforce Files linked to the corresponding Account, Contact, or Opportunity. Salesforce's default file size limit of 25MB per file applies. Inline images embedded in notes are extracted and rehosted as separate Files.

Origo BPO workflows, staffing rules, SLA triggers, and notification automations do not transfer to Salesforce. These require manual rebuild in Salesforce Flow or Apex after migration is complete. FlitStack exports the rule definitions as a structured reference document your Salesforce admin can use during the rebuild phase.