Migrate from Capsule CRM to Salesforce Sales Cloud

Capsule Party records with type=person map to Salesforce Contact. The contact's name fields map to FirstName and LastName; email maps to Email; phone maps to Phone; address fields map to MailingStreet, MailingCity, MailingState, and MailingPostalCode. The original Capsule Party ID is preserved in a custom field capsule_party_id__c for audit and cross-reference.

Capsule Party records with type=organisation map to Salesforce Account. Organisation name maps to Account Name; website maps to Website; phone maps to Phone; address fields map to BillingStreet, BillingCity, BillingState, and BillingPostalCode. We create Account records before Contact records so that AccountId can be resolved on each Contact at insert time.

Capsule relationships between a person Party and an organisation Party indicate that the contact works at or is associated with the organisation. We resolve this by linking the Contact's AccountId to the mapped Account record. Secondary relationships (board member, investor, contractor) are preserved in a custom multi-select picklist on Contact.

Capsule Opportunities map to Salesforce Opportunity with name, value, currency, expected close date, owner, probability, and pipeline stage preserved. The Capsule pipeline name maps to a Salesforce Record Type or Sales Process, and the Capsule stage name maps to Salesforce StageName. Probability percentages migrate from Capsule to Salesforce StageProbability.

Each Capsule pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. For accounts with multiple Capsule pipelines, we create one Record Type per pipeline so that stage values stay scoped per line of business. Stage probability percentages migrate from Capsule to Salesforce StageProbability with rounding to the nearest allowed integer.

Capsule Cases map to Salesforce Case if the destination org includes Service Cloud. Case status, priority, assignee, description, and linked Party reference migrate. If the destination does not include Service Cloud, we map Cases to a custom Case__c object with the same field structure. Conversation history from Capsule Cases migrates as Task records linked to the Case or custom object.

Capsule Projects are available on Starter and above plans. We migrate project name, status, and milestones. Project milestones map to Salesforce Tasks with a custom milestone_flag__c checkbox set to true and the parent Project name in a custom project_name__c field. If the destination Salesforce org has high project management volume, we offer a custom Project__c object as the parent instead of using Tasks.

Capsule custom fields are created via Capsule's data-tag system and are not returned with entity records by default. We query /fields/definitions for each entity type before pulling record data, resolve list field options, and apply the correct type casting (text, date, numeric, list) to values. Text fields map to Salesforce Text; date fields map to Date; numeric fields map to Number; list fields map to Picklist or Multi-Select Picklist depending on whether Capsule allows multiple selections.

Capsule tags are flat labels applied to Parties, Opportunities, and Cases. We map tag names to a custom Tags__c multi-select picklist on the relevant Salesforce object. Where the customer uses tags for content classification, we offer Topic and TopicAssignment as an alternative with a topic naming strategy agreed during scoping.

Capsule email activities migrate to Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). The WhoId on Task points to the Contact or Lead; the WhatId points to the related Opportunity, Account, or Case. Direction (inbound/outbound) is preserved in a custom field.

Capsule call activities map to Salesforce Task with TaskSubtype set to Call. Call disposition, duration (stored in seconds), and any notes migrate to custom Task fields. Activity timestamp becomes ActivityDate on the Salesforce Task.

Capsule meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attendee mapping links to EventRelation records pointing at the relevant Contacts and Users. The Capsule meeting description migrates to Event Description.

Capsule note activities migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Case. Note body migrates as plain text. If Capsule notes contain attachments, those migrate as ContentDocument records linked to the same parent.

Capsule Tasks (standalone tasks not attached to an activity) map to Salesforce Task. Due date, assignee, status, and description preserve. Task assignment migrates by resolving the Capsule user reference to the Salesforce User mapping established during owner reconciliation.

Capsule users map to Salesforce User records by email address match. Any Capsule user without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved in a custom field.