Migrate from OpenCRM to Salesforce Sales Cloud

OpenCRM Company records map directly to Salesforce Account. The Company name becomes Account Name, domain fields map to Website, and industry or sector fields map to Industry or a custom picklist. Account is the first object imported in all cases because Contacts carry a foreign-key reference to their parent Company. We validate that every Contact in the export has a valid Company before staging the import; orphaned Contacts (those with no parent Company) are flagged for the customer to resolve or to allow as standalone Contacts in Salesforce.

OpenCRM Contact records map to Salesforce Contact. The AccountId lookup is resolved at migration time using the OpenCRM Company name as the matching key against the Account Name field, then cross-referenced to the Salesforce AccountId. Email address is used as a secondary dedupe check. Any Contacts without a valid Salesforce AccountId are held in a queue for resolution before import. Custom fields on Contact are mapped field-by-field during scoping, with type conversion applied (OpenCRM date pickers become Salesforce Date fields, checkbox fields map directly, and text fields map to Text or Long Text Area depending on content length).

OpenCRM Deals map to Salesforce Opportunity. Deals that reference a Company map to Opportunity with AccountId resolved via the Company-to-Account mapping. Deals that reference a Contact directly require special handling: we set the Opportunity Contact Role to the Contact after Opportunity creation. Deal value maps to Amount, expected close date maps to CloseDate, and owner assignment maps via the Owner reconciliation step.

OpenCRM allows full customisation of pipeline stage names per workflow, which means stage values are tenant-defined and almost never align 1:1 with Salesforce StageName values. We produce a stage-mapping table during scoping, present it to the customer for sign-off, and apply the mapping during the Deal import so each Opportunity lands in the correct Salesforce stage. Stage probability values migrate from OpenCRM to Salesforce StageProbability with rounding to the nearest integer.

OpenCRM Activities (calls, meetings, tasks) are stored with date/time formats and owner fields that differ from Salesforce's UTC-normalised timestamps. We normalise all timestamps to UTC before loading, map OpenCRM owner names to Salesforce User IDs via the Owner lookup table, and import Activities as Salesforce Task (for calls and tasks) or Event (for meetings) records. Parent-entity linkage is resolved using the Contact or Company name lookup to produce the correct WhoId and WhatId on each activity record.

OpenCRM Notes attached to contacts, companies, or deals migrate to Salesforce Note records. We preserve the parent-entity linkage by resolving the OpenCRM record reference to the corresponding Salesforce record ID (ContactId, AccountId, or OpportunityId) at migration time. Note body migrates as plain text; rich formatting is converted where possible and flagged where conversion is not supported.

File attachments stored against contacts, companies, or deals in OpenCRM are extracted via the UI and stored to a file store. We generate reference links in Salesforce and attach them via ContentDocumentLink to the corresponding Contact, Account, or Opportunity. PDF, DOCX, XLSX, PNG, and JPG formats are handled; unsupported binary formats are listed in the delivery document with a note to the customer on manual retrieval.

OpenCRM owner assignments on Contacts, Companies, and Deals are mapped to Salesforce User records by email address. We build a lookup table during the scoping phase and match on exact email. Any OpenCRM Owner that does not have a corresponding Salesforce User record is flagged in the reconciliation queue for the customer's Salesforce admin to provision before record import resumes. Ownerless records (unassigned Deals or Contacts) are flagged separately.

OpenCRM tag-based categorisation on contacts and companies migrates to Salesforce multi-select picklist fields on Contact and Account. Tags with fewer than 15 distinct values map cleanly; tags with high cardinality are flagged for the customer to choose between a multi-select picklist, a separate custom object, or Topics.

OpenCRM custom fields on all primary objects (Contact, Company, Deal) are discovered per-tenant during scoping. Each custom field is mapped to an equivalent Salesforce custom field (with __c suffix) of matching or nearest-matching type. OpenCRM text custom fields map to Text; date fields map to Date; numeric fields map to Number or Currency depending on content. Custom field metadata (label, API name, data type, picklist values) is documented in the scoping deliverable before any data is touched.

OpenCRM email marketing campaigns and their associated subscriber lists map partially to Salesforce Campaign and CampaignMember. We export the campaign name, list members, and opt-in status. Email content (templates, HTML bodies, images) does not migrate automatically; we deliver a campaign inventory document listing each OpenCRM campaign with its recipient list and recommended Salesforce CampaignMember Status values for the customer to rebuild in Salesforce Marketing Cloud or a third-party email tool.

If OpenCRM Products are in scope, they map to Salesforce Product2 records with Standard Price Book entries created during import. Product code maps from OpenCRM SKU fields. Pricebook2 is set to the Salesforce org's Standard Pricebook for all line-item imports.