Migrate from CASH to Salesforce Sales Cloud

CASH contacts map directly to Salesforce Contacts. CASH stores a company name property on each contact — this resolves to AccountId in Salesforce, requiring a corresponding Account record to exist first. If CASH contacts have no company association, they link to a default 'Unassigned' Account record.

CASH does not have standalone company objects; company data lives as properties on contacts. FlitStack extracts unique company names from CASH contact records and creates Salesforce Account records first, then populates AccountId on the corresponding Contacts. Company domain from CASH becomes Account.Website.

CASH transaction records map directly to Salesforce Opportunities. Transaction amount maps to Opportunity.Amount, transaction date maps to Opportunity.CloseDate, and transaction status maps to Opportunity.StageName via value mapping. Each CASH transaction requires a Contact or Account link in Salesforce for proper relationship establishment. Primary contact associations are created via OpportunityContactRole records after contact migration completes.

CASH transaction statuses (e.g., 'Open', 'Won', 'Lost', 'Pending') require explicit mapping to Salesforce Opportunity StageName pick-list values. Stage probability percentages and forecast category assignments re-apply based on your Salesforce stage configuration. Any custom CASH status labels require explicit value mapping before migration begins, as Salesforce does not accept unlisted pick-list values during data insertion.

CASH email activity logs map to Salesforce Tasks with Type='Email'. Subject, body content, timestamp, and owner email are preserved during migration. Task links to WhoId (Contact) and optionally WhatId (Opportunity or Account) using relationship lookups established in earlier migration phases. Original CASH activity ID is stored as Source_System_Activity_ID__c custom field for audit trail purposes.

CASH call logs map to Salesforce Tasks with Type='Call'. Duration, call outcome, timestamp, and owner email are all preserved during the migration. Call disposition information from CASH maps to Task.CallDisposition if that field is present, otherwise it is stored as Call_Outcome__c custom field on the Task record. Both options preserve the original disposition data for reporting continuity.

CASH meeting records map to Salesforce Events. Meeting subject, start time, end time, location, and description are preserved. CASH meeting attendees linked to Contacts are not directly migratable — Salesforce Events have no native attendee object at the standard level; attendee data is stored as Meeting_Attendees__c custom field.

CASH custom properties on contacts (text, number, date, pick-list, currency types) become Salesforce custom fields on the Contact object. Custom field names use the __c suffix. Field-level security and page layout assignment happen in Salesforce before migration. Pick-list custom properties require value set creation in Salesforce.

CASH custom properties on transactions map to Salesforce custom fields on the Opportunity object. Currency-type custom properties from CASH map to Salesforce Currency fields or Number fields depending on your decimal precision requirements and whether Salesforce Multi-Currency is enabled in your org. All Salesforce custom fields require setup in Object Manager before data insertion — FlitStack creates them during the setup phase if they do not already exist.

CASH stores owner as an email address on each record. FlitStack resolves CASH owner emails to Salesforce User records by matching User.Email. Unmatched owners are flagged before migration — your team either creates Salesforce users for them or assigns their records to a fallback owner. No record lands without a valid Salesforce OwnerId.

CASH notes attached to contacts or transactions map to Salesforce Notes (the enhanced Notes object, not legacy Note). Note title, body, parent record link, and created date are preserved. Notes without parent links are attached to the default Account as reference notes.