Migrate from Star CRM to Salesforce Sales Cloud

Star CRM's Contact records map to Salesforce Lead or Contact depending on qualification status. If Star CRM does not distinguish Leads from Contacts, we apply a split rule during migration based on the presence of a converted company, deal association, or a custom status property. Contacts with associated Deals and Company links become Salesforce Contacts attached to Accounts; Contacts without deal history and no converted status become Salesforce Leads. We preserve the original Star CRM contact ID in a custom field starcrm_id__c on both Lead and Contact for reconciliation.

Star CRM Company records map directly to Salesforce Account. Company name becomes Account Name; address fields map to BillingAddress composite fields or individual Street, City, State, PostalCode, Country fields. Company is imported before Contact so that the AccountId lookup is satisfied at Contact insert time. We use company name as the dedupe key during Account import to prevent duplicate Account creation.

Star CRM Deals map to Salesforce Opportunity with stage and value preserved. The Star CRM deal stage maps to Salesforce StageName using an explicit stage mapping defined during scoping. Deal owner maps to Salesforce OwnerId via the User lookup. Closed-Lost and Closed-Won dates migrate as CloseDate and a custom starcrm_closed_date__c field if the original timestamp is required for historical analysis.

Star CRM pipeline stages are enumerated during discovery and mapped to Salesforce Opportunity Stage values. We configure the destination Salesforce Sales Process to whitelist the relevant stages. Probability percentages from Star CRM migrate to Salesforce StageProbability, rounded to the nearest integer. If Star CRM has more stages than Salesforce's default 10-stage picklist, we add custom stage values during sandbox configuration.

If Star CRM supports multiple Deal pipelines, each maps to a Salesforce Record Type on Opportunity with a corresponding Sales Process. Record Types enable different page layouts and stage sets per line of business. We pre-create Record Types in the Salesforce Sandbox during schema design and deploy to production before data migration begins.

Star CRM Activities map to Salesforce Task (calls and generic activities), Event (meetings), and EmailMessage (emails) records. Activity type is preserved via TaskSubtype (Call) and custom activity_type__c fields. ActivityDate and timestamps migrate to Salesforce ActivityDate, StartDateTime, and EndDateTime as applicable. We use the Bulk API 2.0 to handle large engagement volumes without triggering Salesforce's per-day API limits. The WhoId links the activity to the migrated Lead or Contact; the WhatId links to the related Opportunity or Account.

Star CRM owner references map to Salesforce User records via email matching. We extract every distinct owner across Contacts, Companies, Deals, and Activities and match against the destination Salesforce org's User table. Owners without a matching User are held in a reconciliation queue for the customer's admin to provision. Salesforce requires a valid OwnerId on Opportunity and Contact, so User provisioning must complete before record import begins.

If Star CRM distinguishes Lead records from Contact records, we migrate Leads directly to Salesforce Lead. Lead source, status, and any scoring fields migrate to corresponding Salesforce Lead fields or custom fields if no standard equivalent exists. We preserve the original Star CRM lead ID in starcrm_lead_id__c.

Star CRM custom contact properties require live discovery before field mapping. We export a sample Contact record set during scoping, infer the actual property names and data types from the observed data, and map each to a typed Salesforce custom field. Custom properties on Contact that have no standard Salesforce equivalent become custom fields with the appropriate data type (Text, Number, Date, Picklist, Checkbox). The __c suffix is appended per Salesforce convention.

Star CRM custom Deal properties migrate to custom Opportunity fields. We apply the same discovery process: sample export, property name inference, type mapping, and custom field creation in the Salesforce org before migration. Stage-specific custom properties require Salesforce field creation before the Deal-to-Opportunity mapping phase.

Star CRM tags on Contacts or Deals migrate to Salesforce multi-select picklist fields if tag count is small (under 50 unique tags). If tag volume is large or tags represent dynamic classification, we migrate them as a custom text field or integrate with Salesforce Topics for content-based tagging. The customer chooses the tag strategy during scoping based on how tags are used in reporting.

Star CRM exports attachments as individual files per record, each named by the system without parent-record context in the filename. We download all attachment files, build a manifest linking each file to its parent record ID or name, then upload them to Salesforce as ContentVersion records. We create ContentDocumentLink records to attach each ContentVersion to the correct parent (Contact, Lead, Account, or Opportunity). This step adds time proportional to attachment volume. Files without a resolvable parent record are flagged for manual review.

Star CRM user records (internal team members) map to Salesforce User records. We resolve by email address. Active and inactive status is preserved. If Star CRM stores role or department information, we map it to Salesforce Role and Department fields. Archived or deactivated Star CRM users are migrated as inactive Salesforce Users if the customer requests retention of historical assignment data.