Migrate from Optimiser CRM to Salesforce Sales Cloud

Optimiser CRM Contact records with status indicating unqualified prospect (Lead status, new inquiry, unqualified) map to Salesforce Lead. Contacts with status indicating active relationship, customer, or closed-won map to Salesforce Contact tied to an Account. We enumerate the customer's Optimiser status values during scoping and build a status-to-object mapping table before migration. The original Optimiser status value is preserved in a custom field ocrm_original_status__c on both Lead and Contact for audit and reporting continuity.

Optimiser CRM Company records map directly to Salesforce Account. Company name becomes Account Name; domain or website data maps to the Website field where available. We use Account Name as the dedupe key during import to prevent duplicate Account creation. Account records are inserted before Contact records so that AccountId lookup references are satisfied at the moment of Contact insert.

Optimiser CRM Deals map to Salesforce Opportunity. The Deal amount, expected close date, owner assignment, and custom fields migrate directly. Pipeline stage names from Optimiser are mapped to Salesforce Stage values via a stage-mapping table we build during scoping; stages with zero records in Optimiser are excluded from the destination Salesforce stage set. Closed-Lost and Closed-Won custom fields from Optimiser become Salesforce Loss Reason and custom win/loss date fields.

Optimiser CRM Lead records map directly to Salesforce Lead. Lead status, source, and score fields migrate to corresponding Salesforce Lead fields. Any custom fields on the Optimiser Lead object are created as Salesforce custom fields (with __c suffix) and mapped before import. The source field names are preserved in the mapping table for the customer's admin to reference during post-migration validation.

Optimiser CRM Activities (calls, emails, meetings, notes) logged against Contacts or Deals export as activity records with parent record references. Calls map to Salesforce Task with TaskSubtype = Call. Emails map to Salesforce EmailMessage records linked to a Task. Meetings map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Notes map to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. We resolve the WhoId (Contact or Lead) and WhatId (Opportunity or Account) on each activity during the transform phase before bulk API insert.

Optimiser CRM User records carry name, email, and role. We map Optimiser users to Salesforce User records by email address as the match key. Any Optimiser Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision the User before record import resumes. OwnerId references on Deals and Activities cannot be resolved without an active Salesforce User record.

Optimiser CRM allows configurable pipeline stages per deal type with no documented limit on stage count. We extract the full stage list during scoping and create a Salesforce Opportunity Stage value set that mirrors the source. Stage probabilities from Optimiser are mapped to Salesforce StageProbability values, rounded to the nearest integer that Salesforce accepts. Stages with zero records in Optimiser are not created in Salesforce to keep the stage set lean.

Optimiser CRM supports custom properties on Contacts, Companies, and Deals with schema varying per instance. We enumerate every active custom field during scoping via a trial export, excluding fields with zero data values. Each Optimiser custom field is created in Salesforce as a custom field with the appropriate type (text, number, picklist, date, checkbox, etc.), and the mapping is documented in the field inventory. Custom field values transfer directly where types are compatible; type mismatches (e.g., Optimiser free-text storing numeric values) require explicit transform logic.

Tags applied to Contacts or Deals in Optimiser CRM export as label values. We migrate tags as multi-select picklist values in Salesforce. If the destination org uses Salesforce Topics, we can alternatively create Topic and TopicAssignment records during migration. The customer chooses tag strategy during scoping. Tags with values that exceed Salesforce picklist length limits are truncated and flagged in the mapping documentation.

Optimiser CRM includes project management modules alongside CRM data. If the customer requests Project migration, we create a Salesforce custom object Project__c with fields mapped from the Optimiser Project schema. Projects often have lookups to Company (Account) and Contact records, so Project migration runs after Account and Contact inserts to satisfy those relationships. If the destination Salesforce org uses a project management tool (such as Salesforce Flow for project tracking, a PSA tool, or a third-party integration), we recommend that Projects be migrated last and the customer's admin confirm the destination schema before migration.

Document attachments referenced by URL or stored in Optimiser CRM's file store are downloaded locally during the extraction phase, then uploaded to Salesforce as ContentVersion records and linked to the correct parent record via ContentDocumentLink. The parent record (Contact, Account, Opportunity) must exist in Salesforce before the ContentVersion upload so that the ContentDocumentLink can reference it. Attachments over 25 MB in Optimiser are flagged for manual review because Salesforce has a 25 MB per-file limit for ContentVersion.

Optimiser CRM workflows, assignment rules, and triggered sequences are stored in the platform's proprietary logic layer and are not accessible via export. We do not migrate automations. During scoping, we collect every automation the customer identifies, document its trigger type, conditions, actions, and recommended Salesforce Flow equivalent, and deliver this as a written rebuild checklist. Each automation adds 1-2 hours to the scoping timeline. The customer's admin or a Salesforce partner rebuilds them post-migration.