Migrate from Composity CRM to Salesforce Sales Cloud

Composity Accounts map 1:1 to Salesforce Account. The Account Name, address fields, industry, and status fields migrate directly. Any Composity custom properties defined on Account (via the Custom Data module) reverse-engineered at scoping time become Salesforce custom fields on Account. We use Account Name as the dedupe key during import.

Composity Contacts map to Salesforce Contact. The Account-Contact relationship is preserved by resolving the Composity Account reference to the Salesforce AccountId at migration time. Role, email, phone, and custom contact properties map to typed Salesforce fields. Owner assignments migrate by email match against the Salesforce User table.

Composity Leads from the Campaign & Lead Management module map to Salesforce Lead. Lead status, source, and qualification data transfer to Lead Status, LeadSource, and custom qualification fields. We preserve any HubScore or lead quality rating from Composity in a custom field comp_lead_score__c.

Composity Deals (from the Sales submodule) map to Salesforce Opportunity. Stage names are custom-configurable per Composity organization, so we export the full stage definition during discovery and configure matching Salesforce Stage values and probabilities before migration. Close date, deal value, and expected revenue map directly. Owner assignments resolve via email-to-User lookup.

Composity pipeline stages are user-defined per tenant. We export the complete stage list including name, order, and win/loss flags and recreate them as Salesforce Stage values within a Sales Process we configure pre-migration. Stage probability percentages map to StageProbability, rounded to the nearest integer Salesforce allows.

Composity Invoices from the Sales module map to Salesforce Invoice (available from Professional tier) with header fields, line items, tax codes, and payment status. Partially paid invoices require balance carry-forward logic and are flagged during scoping. If the destination Salesforce org does not include Invoice, we map to a custom Invoice object with equivalent field structure.

Composity Product catalog entries (name, SKU, price, description) map to Salesforce Product2 records. We create Standard Pricebook entries during import. Custom pricing rules defined in Composity migrate as custom fields on Product2 or as PricebookEntry custom fields.

Composity Projects module (Growth tier and above) stores project name, status, dates, and assigned resources. Salesforce has no native project object in Sales Cloud, so we design a custom Project object during scoping with fields mapped from Composity. Custom project fields and milestone definitions require explicit mapping at scoping and pre-creation in the destination org.

Composity's Production module stores manufacturing or job data with BOM (bill of materials) references and production order records. Salesforce has no native equivalent. We extract production records, pre-create a Production_Order__c custom object with BOM reference fields, and map production order status, quantity, and related product data. This requires schema design during scoping and is not a standard field-to-field migration.

Composity Inventory records (SKU, quantity, warehouse location, reorder levels) map to Salesforce Product2 if stock tracking is not required. If full inventory management is needed, we design a custom Inventory_Item__c object. Any negative stock or quantity discrepancies existing in Composity at migration time are flagged and documented in the reconciliation report.

Composity Document Storage exports files one at a time. We build a file inventory during discovery, download files in parallel where possible, and upload them to Salesforce as ContentVersion records linked to the parent record (Account, Contact, Opportunity) via ContentDocumentLink. Filename and metadata matching determines the correct parent record attachment.

Composity activities (calls, emails, meetings, notes) linked to Contacts and Accounts map to Salesforce Task (TaskSubtype=Call for calls), Event, EmailMessage, and Note records. Activity type, date, description, and linked record reference transfer directly. We resolve WhoId (Contact or Lead) and WhatId (Account or Opportunity) references at migration time.

Composity custom fields defined in the Custom Data module apply to any object. We reverse-engineer the custom field schema during discovery by inspecting exported CSV headers against the standard Composity field set, generate a field-level mapping for each affected object, and pre-create the custom fields in Salesforce (with __c suffix) before data import begins.

Composity users with login credentials, roles, and permissions export as records with email, name, and role data. We match by email against the Salesforce destination User table. Any Composity user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated records depend on this resolution.