Migrate from Cirqll to Salesforce Sales Cloud

Cirqll Customers map to either Salesforce Lead or Contact depending on the customer's qualification status in Cirqll. We use the Cirqll Lead object's qualification status and source attribution fields to determine the split: unqualified prospects become Salesforce Leads; qualified buyers with an associated company become Salesforce Contacts attached to an Account. The original Cirqll Customer record identifier is preserved as an external ID on both Lead and Contact for reconciliation.

Cirqll Lead records migrate directly to Salesforce Lead. Qualification status, source attribution, and owner assignment transfer as standard Lead fields. Any Cirqll custom properties on the Lead object transfer to Salesforce custom Lead fields we provision during schema design. Owner resolution happens via email match against the Salesforce User table.

Circl Customers with an associated company record map to a Salesforce Account first, then to a Contact attached to that Account. The Account is created before Contact insert so that AccountId is satisfied at the moment of Contact import. The Cirqll company name becomes the Account Name; the Customer email and phone transfer to Contact.

Cirqll Task records map to Salesforce Task with Status, Priority, ActivityDate, and description preserved. Open and completed task states carry forward. Task assignment migrates by resolving the Cirqll owner reference to a Salesforce User via email match. Cirqll does not expose task subtypes, so all tasks import as standard Tasks; any categorization the customer applies in Cirqll migrates to a custom Task Type picklist.

Cirqll Activity records with type = call map to Salesforce Task with TaskSubtype set to Call. Call duration and any disposition notes from Cirqll transfer to custom Task fields we provision during schema design. The Activity timestamp becomes the Task ActivityDate to preserve timeline ordering.

Cirqll Activity records with type = meeting map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee lists from Cirqll meeting records become EventRelation records pointing to the resolved Leads, Contacts, and Users in Salesforce.

Cirqll Activity records with type = email map to a Salesforce Task (the activity timeline entry) linked to an EmailMessage record (the email content). The WhoId on Task points to the resolved Lead or Contact; the Subject and body transfer to EmailMessage Subject and TextBody respectively.

Cirqll Notes attached to Contacts or Leads migrate as Salesforce Note records linked via ContentDocumentLink to the parent Lead or Contact. Note body migrates as plain text; any rich formatting in Cirqll is preserved as-is. The Note creation timestamp transfers to Salesforce to maintain the original audit trail.

Cirqll Calendar Events migrate to Salesforce Event with StartDateTime, EndDateTime, Subject, and attendee list preserved. All-day event flags require field-level mapping since Salesforce handles all-day events with a separate Date field (而非 DateTime). Recurrence patterns from Cirqll migrate to Salesforce Event recurrence fields if present; if the recurrence model differs, we flag it for manual review.

Cirqll User accounts migrate as owner mappings in Salesforce. We resolve Cirqll User references by email match against the Salesforce User table. Active vs. inactive status carries forward; role-based permissions do not transfer because Salesforce's permission model is destination-defined. Any Cirqll User without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import resumes.

Cirqll documents are binary blobs stored separately from the API-accessible data layer and do not export via standard API endpoints. We handle document migration as a secondary pass using a download-and-reupload workflow: we identify document-record relationships during scoping, download files with original filenames and upload timestamps preserved, and reattach them to the corresponding Salesforce records (Contact, Lead, Account, or Opportunity) as ContentDocument records via the Salesforce API. This pass runs after the primary data migration and requires the customer to confirm their Salesforce storage allocation.

Cirqll's activity tracking across calls, emails, and meetings provides a shared history per Contact or Lead. In Salesforce, this history spans Task (calls, tasks, emails), Event (meetings), and EmailMessage (email content) objects. We stitch these together via the WhoId (Lead or Contact) and WhatId (Opportunity or Account) lookups so that the full activity timeline is visible on the Contact or Lead record in Salesforce. Activity timestamp ordering is preserved by setting ActivityDate to the original Cirqll timestamp.