Migrate from Combit CRM to Salesforce Sales Cloud

Combit CRM's address model stores physical locations as Anschriften records that link to one or more Kontakte (Contacts) via a relational key. We extract the address table (including fields for street, city, postal code, country, and any custom address fields), then write the address values directly into Salesforce's standard MailingAddress and ShippingAddress compound fields on the Contact object. For accounts with multiple billing or shipping addresses, we create a custom Address__c object with a Contact__c lookup to preserve the multi-address structure, with IsPrimaryAddress__c as a boolean flag for default resolution.

Contacts are the core object in Combit CRM. We migrate contact records with their standard fields (first name, last name, email, phone, job title) and resolve the parent Address (Anschriften) reference at Contact insert time. Combit stores the contact-address relationship as a separate link table; we denormalize that link into the Contact's address fields during the transform phase. Any Combit contact without an associated address gets a blank mailing address in Salesforce, flagged in the reconciliation report.

Combit CRM's firm records hold organizational data and serve as the parent entity for related contacts. We map these to Salesforce Account, using the firm name as the Account Name and the firm's industry and website fields where populated. The Combit firm-contact relationship (which contacts belong to which firm) becomes a Contact.AccountId lookup that we resolve at migration time. If Combit does not enforce a firm-contact hierarchy, we allow Account-less Contacts in Salesforce and flag them for the customer's admin to assign during post-migration cleanup.

Deals in Combit CRM map directly to Salesforce Opportunity. We map the deal value to Amount, expected close date to CloseDate, owner to OwnerId (via email reconciliation), and deal stage to StageName. Combit's custom pipeline stages become Salesforce Opportunity Stage values, and we configure a Sales Process in Salesforce that whitelists only the relevant stages per pipeline before migration begins.

Each Combit deal pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that limits the StageName picklist to that pipeline's stage values. We map probability percentages from Combit to StageProbability on each StageName entry, rounding to Salesforce's allowed integer range. Closed-Won and Closed-Lost stages carry a probability of 100 and 0 respectively.

Combit Projects can span multiple contacts, activities, and deal associations. If the project represents a pre-sale engagement (discovery, scoping), we map it to a Salesforce custom object Project__c with lookups to Account and Contact. If the project represents a post-sale delivery, we map it to Opportunity, using the Combit project budget as Amount and project dates as CloseDate and a custom ProjectStartDate__c. The customer selects the strategy during scoping. We flag any Combit project that has a linked Deal and recommend Opportunity mapping to preserve the revenue reporting relationship.

Combit activity records of type call map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition notes, and timestamp migrate to CallDurationInSeconds, Description, and ActivityDate respectively. The parent contact or project reference resolves to a WhoId (Contact or Lead) or WhatId (Opportunity, Account, or custom Project__c) at migration time.

Combit meeting activities map to Salesforce Event with StartDateTime, EndDateTime, Location, and Description preserved. Attendee lists from Combit migrate as EventRelation records linking the Event to the relevant Contact, Lead, or User records. We preserve the chronological order of meetings by setting the Event StartDateTime to the original Combit timestamp.

Combit task activities (Aufgaben) map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. The assigned user resolves via email match to Salesforce OwnerId. Tasks without a resolved owner are imported with CreatedById set to the migration service user and flagged in the reconciliation report for manual assignment.

Combit notes attached to contacts, companies, or projects migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Project__c. Rich text formatting from Combit converts to Salesforce's rich-text Note body. Standalone notes without a parent record migrate to the importing user's personal notes folder and are flagged for reassignment.

Combit CRM allows extensive user-defined fields across all standard objects. We identify every custom field definition during discovery (field name in German, data type, picklist values), translate the labels to English equivalents for Salesforce, and map the Combit data type to the closest Salesforce field type (text to Text, number to Number, date to Date, picklist to Picklist, multi-select to Multi-Select Picklist). We pre-create all custom fields in the destination Salesforce org before any data import, using the Combit field name as the field label and a sanitized API name (no umlauts, spaces replaced with underscores). Validation rules that existed on Combit custom fields are documented and recommended for reimplementation as Salesforce validation rules post-migration.

Combit user records define ownership of contacts, deals, and activities. We extract all distinct owner email addresses referenced on migrating records and match them against the destination Salesforce org's User table by email. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. We preserve the original Combit owner name as a custom field combit_owner_name__c on the migrated record for audit trails. Inactive Combit users map to inactive Salesforce Users if the customer wants to retain historical assignment.

Combit CRM file attachments migrate to Salesforce ContentDocument linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Project__c. We extract attachments to a file store, preserve the original filename and MIME type, create a ContentVersion record (Title, VersionData, ContentLocation = 'E'), and then link it with a ContentDocumentLink record pointing to the target Salesforce record. Large attachments (over 25 MB) exceed Salesforce's single-file upload limit and require chunked upload via the API.

Combit CRM categorical tags on records migrate to Salesforce either as a custom multi-select picklist field on the relevant object or as Salesforce Topics with TopicAssignment records, depending on how the customer intends to use tagging in Salesforce. We extract the distinct tag values per object during discovery, present both options to the customer, and implement their chosen strategy during the transform phase. Multi-value Combit category fields become comma-delimited multi-select picklist values in Salesforce.