Migrate from Cirrus CRM to Salesforce Sales Cloud

Cirrus CRM Company records map directly to Salesforce Account. The company's credit information and geographic enrichment (latitude/longitude) map to custom fields on Account if the destination org uses them. We use the company name as the dedupe key and create Accounts before any Contact or Deal import so that the AccountId lookup is satisfied at insert time. The customer confirms whether Cirrus CRM's built-in credit rating should land as a custom field or be excluded based on whether Salesforce has an equivalent ERP-fed credit module.

Cirrus CRM Contacts map to Salesforce Contact. Name, email, phone, and address fields migrate directly. We preserve the Contact-to-Company relationship via AccountId using the parent Account record's external ID or Salesforce-generated ID. Custom fields on Contact require type validation (text, number, date, picklist) via a 50-record test batch before full import, because Cirrus CRM per-tenant custom field schemas are not universally exported.

Cirrus CRM User records map to Salesforce User by email match. Owners on Deals and Activities are resolved via this User lookup. Any Cirrus CRM User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Cirrus CRM users map to inactive Salesforce users if historical assignment is required.

Cirrus CRM Deals map to Salesforce Opportunity. The deal amount, close date, and stage label migrate directly. Stage label from Cirrus CRM becomes a static text field or maps to a Salesforce StageName value depending on whether the customer confirms they want the pipeline definition migrated as configuration. Historical stage movement timestamps migrate to Salesforce OpportunityHistory if available in the Cirrus CRM export. AccountId and OwnerId are resolved at migration time via the Company and User lookups.

Cirrus CRM Pipeline definitions (stage order, win/loss criteria, automation triggers) are not exported with deal records; they live in the pipeline configuration. We treat stage labels as static text unless the customer explicitly confirms they want the pipeline definition migrated. In that case, we configure Salesforce Record Types and Sales Processes with stage values and probabilities matching the Cirrus CRM pipeline configuration, and deploy them to a Sandbox for validation before production migration.

Cirrus CRM Quotes map to Salesforce Quote (Sales Cloud standard object from Professional tier). Quotes carry line items and product associations. The Quote-to-Deal relationship (Cirrus CRM Quote references Deal) maps to Quote's OpportunityId pointing to the migrated Opportunity. Quote PDFs and formatted documents migrate as ContentDocument attached to the Quote record. The customer confirms whether Quotes should land as Salesforce Quote line items or be simplified into the Opportunity as amount-only.

Cirrus CRM Orders map to Salesforce Order (Service Cloud standard object available from Professional tier). Orders reference both a Quote and a Deal via ERP lineage. We resolve OpportunityId from the migrated Deal and QuoteId from the migrated Quote at migration time. Order status, total amount, and product-line associations migrate. Order-to-invoice relationships from the ERP layer are preserved as custom fields on Order if the customer confirms they need ERP invoice context carried into Salesforce.

Cirrus CRM Products referenced in Quotes and Orders map to Salesforce Product2 records. ProductCode, name, and description migrate. Standard Price Book entries are created during import so that PricebookEntry records are available when Line Items are imported.

Cirrus CRM Quote line items and Order line items map to Salesforce OpportunityLineItem. We resolve Pricebook2Id, Product2Id, and parent OpportunityId at migration time. Quantity, UnitPrice, and TotalPrice migrate directly. If Orders are migrated as a separate object, OrderLineItems are created using the same pattern with parent OrderId resolved.

Cirrus CRM Activities (calls, emails, meetings, tasks) tied to Contact or Deal records migrate to Salesforce as Task (for calls and tasks) or Event (for meetings) records. Email content migrates as EmailMessage linked to a Task. Activity timestamps are preserved as ActivityDate for ordering. WhoId points to the migrated Contact; WhatId points to the migrated Opportunity or Account. We use Salesforce Bulk API 2.0 with chunking for large activity histories to avoid timeout failures.

Cirrus CRM Campaigns track objectives and campaign-level metrics. Campaign names and statuses migrate to Salesforce Campaign. Individual campaign member associations (which Contacts were added to which Campaign) migrate to CampaignMember records. The customer confirms campaign member scope during scoping because large campaign lists can significantly increase migration time and cost.

Cirrus CRM exports attachments as individual files named by record and file type. A Contact with three attachments produces three files. We batch-associate these to the correct destination Salesforce record by filename parsing and re-upload via ContentVersion/ContentDocument/ContentDocumentLink. Files exceeding 10 MB are flagged for manual handling. We provide a manifest mapping each file to its target Salesforce record ID so the customer can verify completeness before go-live.

Cirrus CRM per-tenant custom fields on Contacts, Companies, and Deals require explicit field-by-field mapping because type inference (text, number, date, picklist) must be validated before import. We ask the customer to provide a screenshot or export of their Cirrus CRM field configuration, create the equivalent Salesforce custom fields (with __c suffix) in the destination org, and run a 50-record test batch to validate type mapping before committing to the full dataset.