Migrate from Acumen to Salesforce Sales Cloud

Acumen User records (name, email, department, manager) map directly to Salesforce Contact fields. The Contact's AccountId is resolved from Acumen's organizational unit field or defaulted to a placeholder Account. Original hire date and department translate to custom fields on Contact.

Internal Acumen administrators who will own Salesforce records are matched to Salesforce Users by email. Unmatched admins are flagged before migration — your team either provisions Salesforce User accounts first or assigns a fallback owner for their records. We also store the original Acumen admin identifier in a custom Source_Admin_ID__c field on the Salesforce User record to maintain audit traceability.

Acumen application inventory (name, vendor, category, criticality flag) has no native Salesforce equivalent. We create a custom object with fields for application name, vendor, category, and criticality. This object serves as the parent in the User→Application session relationship. It also includes a Source_System_ID__c field to link each application record back to its Acumen identifier for data lineage.

Acumen session records (user, application, start time, end time, duration) become Salesforce Tasks with Type='Application Session'. Session duration, response time, and application name are stored as custom fields on the Task. Start and end timestamps map to Salesforce Task ActivityDate for reporting.

Acumen's N:N User→Application session relationship requires a custom junction object in Salesforce to preserve the many-to-many link between user and application. The junction stores the SessionId, session start/end, and session quality score as custom fields. Additional metadata such as device type and network latency can also be captured on the junction for deeper IT performance insights.

Acumen Digital Experience Scores (DES, 0–100) per user are stored as a custom Number field (Acumen_DES__c) on the Salesforce Contact record. Historical score snapshots are preserved as JSON-encoded strings in a custom long-text area field for trend reporting. The JSON format allows longitudinal analysis of score changes across periods, enabling identification of engagement trends and seasonal patterns.

Acumen sentiment survey responses (question, answer, score, timestamp) are stored as a custom object linked to Contact. Each survey question becomes a field on this object. Responses are linked to the Contact who submitted them via a lookup relationship. This structure supports aggregated sentiment analysis across respondents, allowing you to filter results by department or time range in Salesforce Reports.

Acumen IT workflow alerts (threshold breach, access denial, anomaly detection) have no direct Salesforce equivalent. We preserve alert records as Tasks with a custom type 'Acumen Alert' and a custom description field, but the trigger logic must be rebuilt in Salesforce Flow.

Acumen organizational units map to Salesforce Account records for department-level grouping. Individual user department assignments also store in a custom Department__c field on Contact. Teams choose whether to use Account hierarchy or a custom field based on reporting needs. The choice influences how cross-department reports are structured in Salesforce Reports, affecting grouping, filtering, and visibility of department metrics.

Acumen report exports and attached documents re-upload to Salesforce Files associated with the relevant Contact or custom object record. File size limits (Salesforce default 25MB per file) apply; larger exports are split into multiple files. We also log each file's original Acumen path in a custom field on the Salesforce File record for traceability and future reference.