Migrate from ContactWise CRM to Salesforce Sales Cloud

ContactWise Contact records map to Salesforce Contact with direct field correspondence for standard fields (name, email, phone, address). Custom contact properties migrate to Salesforce custom fields that we pre-create during schema design, with data type transformation where needed (for example, multi-select picklists converted to comma-separated strings or multi-select picklist fields). Owner assignment maps by email lookup to the Salesforce User table with unresolved owners held in a reconciliation queue.

ContactWise Lead records map directly to Salesforce Lead. The source attribution and lead status fields migrate to Salesforce Lead Status and a custom original_status__c field for audit. We preserve the lead creation date as the Salesforce CreatedDate so that lead aging reports remain accurate after migration.

ContactWise Opportunity records map to Salesforce Opportunity with deal name, amount, stage, expected close date, and owner assignment preserved. Pipeline stage mapping is handled through a stage mapping table documented during discovery, where ContactWise stage names are matched to Salesforce StageName values in the target org's Sales Process. If the destination Salesforce org uses Record Types per pipeline, we apply the appropriate RecordTypeId during import.

ContactWise Company or Account records map to Salesforce Account with company name, domain, address, and industry preserved. Account is the parent of Contact, so we create all Account records before any Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. Owner assignment on Account maps by email to Salesforce User.

ContactWise service desk tickets do not map directly to Salesforce Case because field names, ticket states, and custom properties differ substantially. We perform explicit field-level mapping for every ticket attribute during discovery, validate the mapping in a test migration before running the production import, and preserve ticket-to-contact associations using reference IDs. If the destination Salesforce org does not have Service Cloud enabled, Cases are still available in Sales Cloud at a reduced feature set.

ContactWise pipeline stage definitions are documented during discovery and mapped to Salesforce Sales Process stage values. If the customer uses multiple ContactWise pipelines, we create Salesforce Record Types on Opportunity, each with its own Sales Process that whitelists only the applicable stage values. Stage probability percentages migrate from ContactWise to Salesforce StageProbability.

ContactWise Workflow definitions store automation logic as platform configuration rather than data records. We cannot export and replay these rules directly. We document every active workflow during discovery with its trigger type, conditions, actions, and time-based components, then deliver a written inventory recommending equivalent Salesforce Flow variants (record-triggered, scheduled, or screen flow) and flagging any ContactWise-specific trigger types with no Salesforce equivalent for the admin to address during rebuild.

ContactWise time entries linked to Contacts, Tickets, or Projects do not map directly to standard Salesforce objects. We export time entries with their linked entity reference, duration, date, and billable flag, then map to Salesforce Task records with custom fields for billable_hours__c, time_entry_date__c, and linked_object_reference__c so that billing context is preserved even without a native project object in Sales Cloud.

Documents and attachments associated with Contacts, Opportunities, or Tickets in ContactWise export to cloud storage and are linked in Salesforce via ContentVersion (file content) and ContentDocumentLink (association to parent record). Attachment migration requires careful handling of file type, size limits (Salesforce enforces 25 MB per file via API), and the ContentDocumentLink sharing setting (V for Visible by All Users, I for Internal, C for Controlled by Parent).

ContactWise custom properties on Contact, Lead, Opportunity, and other objects require manual field creation in Salesforce before migration. We identify every custom property during scoping, map data types to equivalent Salesforce field types (text fields, picklists, checkboxes, date fields), create the fields in the destination org before import, and apply transformations where data formats differ. Multi-select picklists in ContactWise map to Salesforce multi-select picklist fields with consistent delimiter handling.

ContactWise owners referenced on Contact, Company, Opportunity, and other records map to Salesforce User by email address match. We extract every distinct owner across all migrating objects and validate against the destination org's User table. Any ContactWise owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision the corresponding User account before record import begins.

ContactWise notes and free-form content linked to Contacts or Opportunities map to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Note body migrates as rich text where supported, and note creation timestamps are preserved as Salesforce CreatedDate to maintain timeline accuracy.