Migrate from Onsite CRM to Salesforce Sales Cloud

Onsite CRM Contacts map to either Salesforce Lead or Contact depending on qualification status. If the Contact has an associated deal or advanced lifecycle state in Onsite CRM, it maps to Salesforce Contact tied to an Account. If it is an unqualified prospect with no deal association, it maps to Salesforce Lead. We preserve the original Onsite CRM contact ID in a custom field onsite_crm_id__c on both Lead and Contact for audit. If Onsite CRM exposes a contact status or lifecycle property, we use it to determine the split rule during scoping.

Onsite CRM Company records map directly to Salesforce Account. Company name becomes Account Name, website maps to Website, and address fields map to the standard BillingAddress compound field. Account is created before any Contact import so that the AccountId Lookup is satisfied at Contact insert. The company-contact association from Onsite CRM is preserved by setting the AccountId reference on each Contact record during migration.

Onsite CRM Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name, deal value maps to Amount, expected close date maps to CloseDate, and the Onsite CRM pipeline stage maps to the Salesforce StageName. We resolve the AccountId (from the associated Company record) and OwnerId (from the associated User record) before Opportunity insert. Any Onsite CRM custom fields on Deal migrate as custom Opportunity fields after the destination schema is confirmed during scoping.

Each custom pipeline stage defined in Onsite CRM becomes a Salesforce StageName value within a Sales Process that we configure in the destination org. Stage order and probability percentages migrate from Onsite CRM to the Salesforce stage setup. If Onsite CRM exposes multiple pipelines, we create a Salesforce Record Type per pipeline so that stage values stay scoped per line of business. All stage configuration happens in a Sandbox org before production migration.

Onsite CRM built-in calling, SMS, and email marketing logs are tracked as activities. We map call activity records to Salesforce Task with TaskSubtype = Call and call duration preserved. SMS logs map to Task with a custom subtype field for SMS. Email logs map to Task records with a custom email flag field. Meeting-type activities map to Salesforce Event with StartDateTime and EndDateTime preserved. The parent record (WhoId and WhatId) is resolved using the Contact or Deal lookup created during earlier migration phases. Note: if Onsite CRM's in-app export does not include rich activity history, we flag this during scoping and advise requesting a separate pre-migration export.

Onsite CRM Task records for follow-ups and reminders migrate as Salesforce Task records with Status, Priority, ActivityDate, and Subject preserved. Task assignment migrates by resolving the Onsite CRM user reference to the Salesforce User via the Owner reconciliation step. Completed status and completion timestamps migrate as Salesforce Task Status = Completed and ActivityDate set to the original completion date.

Any custom fields on Contacts, Companies, Deals, or Activities in Onsite CRM require manual mapping during scoping. We extract the full field list from the CSV export headers, request customer-supplied screenshots of the data structure to confirm what fields the UI exposes, and map each to a typed Salesforce custom field. Custom field type mapping depends on Onsite CRM's data format in the export (text fields become Text, dates become Date, numbers become Number, picklist values become Picklist). We flag any fields that cannot be typed cleanly and resolve the mapping with the customer before migration.

Onsite CRM User records referenced as Deal owners, Task assignees, or Activity owners map to Salesforce User records. We resolve by email match against the destination org's User table during the Owner reconciliation step. Any Onsite CRM User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. User role metadata migrates to Salesforce UserRole if the role hierarchy is defined in Onsite CRM.

Tags applied to Contacts or Deals in Onsite CRM migrate to Salesforce as either multi-select picklist custom fields (if the tag set is closed and small) or as Salesforce Topics with TopicAssignment records (if the tag set is open and content-oriented). The customer chooses the tag strategy during scoping. We normalize tag values during transform to remove special characters that conflict with Salesforce field validation.

Onsite CRM does not appear to have a structured document management or file attachment object in its data model. Any attachments referenced in activity records or deal notes may not be exportable via CSV. We flag document extraction as a manual step during scoping and advise requesting any relevant files directly from the Onsite CRM UI before decommissioning. Salesforce ContentDocument records require separate file upload or a ContentWorkspace setup if the customer has a large document library.

If Onsite CRM exposes a separate Lead object distinct from Contact in its data model or UI, we map it directly to Salesforce Lead. Lead status, source, and scoring properties from Onsite CRM migrate as Salesforce Lead standard and custom fields. If Onsite CRM does not expose a separate Lead object, all unqualified prospects are handled via the Contact-to-Lead split defined in object mapping row 1.

Free-text notes attached to Contacts, Companies, or Deals in Onsite CRM migrate as Salesforce Note records. We preserve the note body, creation date, and last-modified date. If the note author is resolvable via User mapping, we set the CreatedById on the Salesforce Note. Notes are imported after the parent record (Contact, Account, or Opportunity) has been created and validated in Salesforce to avoid orphaned records.