Migrate from ConSol to Salesforce Sales Cloud

ConSol contact records map directly to Salesforce Contact. ConSol stores name, email, phone, company association, and address fields. Salesforce requires an AccountId on Contact — ConSol contacts without a primary company map to a designated 'Unassigned Account' record or the contact lands without an AccountId and is flagged for manual company linkage.

ConSol company records translate to Salesforce Account 1:1. Company name maps to Account.Name, domain to Website, industry to Industry (value-mapping applies for ConSol industry pick-list values that don't match Salesforce's standard pick-list). Employee count and annual revenue map directly when present.

ConSol incident tickets migrate as Salesforce Case records. Case Subject maps from ticket title, Description from ticket body, Case Origin from ConSol's ticket channel field, and Priority from the ConSol priority pick-list. ConSol's SLA timer fields (if configured) are stored as custom datetime fields on Case since Salesforce's native entitlement management is separate configuration.

ConSol service request tickets require a separate Salesforce Case RecordType from incident tickets so page layouts, pick-list values, and assignment rules can differ per request type. We create a 'ServiceRequest' RecordType on Case and map ConSol request-type values to the new RecordType's Stage pick-list.

ConSol project records have no direct Salesforce standard object equivalent. We create a Project__c custom object with fields for project name, status, start/end dates, assigned owner, and linked AccountId. Project-to-ticket linkages are preserved via a lookup relationship from Case to Project__c.

ConSol file attachments on tickets, projects, and contacts are downloaded and re-uploaded to Salesforce Files. Each file becomes a ContentVersion linked to the appropriate Salesforce record (Case, Contact, Account, or Project__c) via ContentDocumentLink. Salesforce's 25MB default file size limit applies; files exceeding this are flagged for manual re-upload to Salesforce Files for Salesforce Content.

ConSol agent and team owner records are matched to Salesforce Users by email address. Unmatched owners are flagged before migration — their ConSol records are assigned to a fallback owner (a designated Salesforce User or Queue) and flagged for reassignment post-migration. Teams and groups map to Salesforce Queues when the ConSol team is a routing entity rather than an individual user.

ConSol custom properties extending tickets become custom fields on the Case object with the __c suffix. Each custom property's data type is evaluated: text fields become Text(255), pick-lists become pick-list fields, date fields become Date fields. Fields are pre-created in Salesforce before data loads begin — we deliver a schema setup plan listing every custom field name, type, and pick-list value so your admin can create them in advance.

ConSol custom properties on contacts and companies map to custom fields on Salesforce Contact and Account respectively. Standard field mappings (name, email, phone) take priority; any remaining custom fields are added as __c fields following the same type-evaluation process as ticket-level custom properties.

ConSol ticket comment threads migrate as Salesforce CaseComment records appended to the corresponding Case. Each comment preserves the author (linked to a Salesforce User where email-match succeeds), timestamp, and body text. If ConSol stores email thread history, it migrates as Salesforce EmailMessage records attached to the Case.

ConSol BPM workflows, automated escalations, SLA rules, and intelligent routing logic have no Salesforce CRM equivalent. They do not migrate as data. FlitStack AI exports ConSol workflow definitions as a reference document your Salesforce admin or implementation partner uses to rebuild equivalent Flow automations post-migration. Workflow rebuild is outside the data migration scope but we provide the artifact.

ConSol's built-in reporting and analytics dashboards cannot be exported and replayed in Salesforce. The underlying data migrates, so report-building can begin immediately in Salesforce with the migrated data. We provide a field mapping reference so your admin knows which ConSol fields correspond to Salesforce fields when rebuilding reports. Report and dashboard rebuild is outside the migration scope but we deliver a source-to-destination field catalog.