Migrate from Spin CRM to Salesforce Sales Cloud

Spin CRM Leads map directly to Salesforce Lead. Standard fields (name, email, phone, status, assigned owner) export via the settings-based CSV from the Lead window and map to Salesforce Lead fields (FirstName, LastName, Email, Phone, LeadSource, OwnerId). Spin CRM lead status values map to Salesforce Lead Status picklist values. We pre-validate the exported column headers against the customer's reported custom field list and request a re-export if columns are missing.

Spin CRM Contacts map to Salesforce Contact with the AccountId lookup resolved from the Spin CRM company association. We export Companies first (as Accounts) and Contacts second so that the AccountId foreign key is present at insert time. Email match is used as the dedupe key if the customer runs multiple import passes. Custom fields on Contacts export via the same CSV mechanism but must be explicitly added to the export view before extraction.

Spin CRM Companies map to Salesforce Account. Company name becomes Account Name, and company address fields map to BillingAddress. Industry, phone, website, and any custom fields export via the CSV and map to the equivalent Salesforce Account fields. We export Companies first to establish the Account record and ID before Contacts that reference them are imported.

Spin CRM Deals map to Salesforce Opportunity. Deal value, stage, owner, expected close date, and associated Contact and Company links migrate. Spin CRM's pipeline is fully customizable with user-defined stage names; we capture the full stage sequence during scoping and replicate it as a Salesforce Sales Process associated with a Record Type. The stage probability matrix from Spin CRM migrates to Salesforce StageProbability values.

Spin CRM pipelines (fully customizable with user-defined stages) map to Salesforce Record Types on Opportunity, each paired with its own Sales Process that whitelists the stage values. The number of Spin CRM pipelines determines the number of Salesforce Record Types we create. If the customer has configured multiple pipelines with different stage sets (for example, an SMB pipeline and an enterprise pipeline), we create separate Record Types so that stage values remain scoped per pipeline context.

Spin CRM Activity records (calls, meetings, notes) may be exportable via CSV but the export mechanism is not explicitly documented. We attempt export through the same settings-based CSV path available for other objects, validate the column headers, and flag any gaps. Call activities map to Salesforce Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. Meeting activities map to Salesforce Event. Notes map to Salesforce Note linked via ContentDocumentLink to the parent record. If the activity export produces insufficient columns, we document the limitation and migrate what is available.

Spin CRM supports custom fields on Leads, Contacts, and Deals. These map to Salesforce custom fields on the equivalent object (Lead__c, Contact, Opportunity) using the __c suffix naming convention. We pre-create all custom fields in Salesforce during the schema design phase before any data import. The customer must add all required custom fields to the Spin CRM CSV export view before extraction; we verify column completeness against the scoping questionnaire and request a re-export if columns are missing.

Spin CRM owner assignments on Leads, Contacts, Deals, and Activities map to Salesforce User records resolved by email match. The customer provisions Salesforce Users before migration begins. We extract the distinct owner list from the exported CSVs and reconcile against the Salesforce User table, flagging any Spin CRM owner without a matching Salesforce User for admin provisioning before record import resumes.

Spin CRM's forecasting capabilities are calculated from deal values and stage probabilities. We extract deal amounts, expected close dates, and stage assignments and map them directly to Salesforce Opportunity Amount, CloseDate, and StageName. Forecasting in Salesforce is handled through standard Opportunity fields, Salesforce Forecasts (available from Group, Professional, Enterprise), or a third-party revenue intelligence app. We do not migrate Spin CRM's internal forecast calculations as a separate object.

Spin CRM includes document storage as a feature, but the export mechanism for attachments is not documented in available sources. We do not attempt to migrate document blobs from Spin CRM without a confirmed export path. We flag this limitation during scoping and recommend the customer export documents manually or retain them in a separate document management system. The document inventory is noted in the migration scope document for the customer's admin.

Spin CRM workflow configurations, automated reminders, and task schedule rules do not have a documented export mechanism and are not migratable as code. We deliver a written inventory of any Spin CRM workflows the customer has configured, describing the trigger, conditions, and actions for the customer's admin to rebuild in Salesforce Flow. This inventory is included as a supplementary deliverable, not as migrated data.

Spin CRM's Standard plan includes territory management. We extract territory assignments as a custom field on the Account or Contact record during export. In Salesforce, territories can be implemented via a custom field, Territory Management (available at Enterprise and Unlimited), or Account Teams depending on the Salesforce edition in use. The customer chooses the approach during scoping.