Migrate from Origo BPO to Nutshell

Origo BPO contact records (name, email, phone, job title, and address fields) map directly to Nutshell Person records. Each contact from Origo BPO lands as a standalone Person entry in Nutshell. When multiple contacts exist per client company, each becomes a separate Person record, and we link each Person to the corresponding Nutshell Company using the companyId reference to maintain the relationship hierarchy.

Origo BPO client organization records map to Nutshell Company records. Fields including company name, address, industry classification, and website URL transfer directly. Parent-subsidiary relationships defined in Origo BPO are preserved using Nutshell's parent-company association field when the source hierarchy is explicitly defined in the export data.

Origo BPO assigns an account manager or service owner per client. We match that owner by email against Nutshell users and assign OwnerId. Unmatched owners are flagged before migration so your team can either create the Nutshell user or reassign before the full run.

Origo BPO tracks service tiers (Gold, Silver, Bronze) or SLA levels that have no native Nutshell equivalent. We create a pick-list custom field (e.g., Service_Tier__c) on the Nutshell Company object and populate it with the source tier values, mapping each value directly from the Origo BPO service tier field.

Origo BPO segments clients by category (mid-market, enterprise, SMB) or internal classification schemes. These values map to a custom pick-list or text field on the Nutshell Company record. The specific field type is chosen based on the cardinality and structure of values in the source export data.

Origo BPO tracks contract value or client revenue in bespoke fields that do not map to a standard Nutshell field. Since Nutshell stores deal amounts on Deals rather than Companies, we create an Annual_Contract_Value__c numeric field on the Company record and optionally mirror the value on the associated Deal record for comprehensive revenue visibility.

Origo BPO service tickets with status, description, and resolution notes map to Nutshell Tasks. The original ticket created date becomes the Task created timestamp; resolved date is stored in a custom field. Each ticket is a standalone Task linked to the relevant Nutshell Person or Company.

Origo BPO email threads archived as text exports map to Nutshell Tasks with Subject and Description fields. Original send dates become the Task due date or created timestamp. Attachments from email threads are downloaded and re-uploaded to Nutshell Files if the export format supports extraction.

Origo BPO call records (date, duration, outcome) migrate as Nutshell Tasks with Type='Call'. The Subject field captures call outcome; the description holds notes. Original call timestamps are preserved. Unmatched contacts without a Nutshell Person record are linked to the associated Company.

Origo BPO meeting records or onsite visit logs map to Nutshell Events with original start/end times, location, and attendees. Attendees without existing Nutshell Person records are created as Person stubs linked to the Company so the Event association is complete.

Origo BPO tracks billing frequency (monthly, quarterly, milestone-based) that has no native Nutshell equivalent. A custom pick-list field (Billing_Frequency__c) on the Company object stores the source value. Revenue recognition logic tied to billing events stays in your accounting tool post-migration.

Origo BPO sometimes tracks how a client was acquired (referral, outbound, partner). A custom text or pick-list field (Referral_Source__c) on the Nutshell Person record captures this if it exists in the source export. If the source does not contain this field, it is noted as a gap.

Origo BPO workflows, SLA escalation rules, and automated alerting logic are BPO-specific constructs that have no functional equivalent in Nutshell's automation model. We export the workflow definitions as a PDF or JSON reference for your team to rebuild in Nutshell's automation tools.

Origo BPO integrations with accounting tools, HR systems, or client portals do not transfer. Each connection must be re-established in Nutshell using Nutshell's API or one of its 100+ integrations. We provide a list of active integrations to your IT team before migration day.