Migrate from CASH to Microsoft Dynamics 365 Sales

CASH API access is not guaranteed — export capability gates the entire migration

CASH platforms vary widely in API coverage. Some lighter CASH tiers expose no public API for record extraction, requiring CSV or manual exports that lose relationship data (contact-to-company links, deal-to-contact roles). Before scoping the migration, FlitStack AI audits the CASH API endpoint availability, authentication method (API key, OAuth, bearer token), and rate limits. If no API exists, we document the export constraints and propose a hybrid approach using CSV enrichment with relationship reconstruction based on CASH report exports. This discovery step is included in the upfront assessment and prevents mid-migration discovery that data cannot be extracted programmatically.

Currency amounts stored as integer cents require explicit division by 100

CASH implementations frequently store monetary amounts as integers in cents (e.g., 1999 representing $19.99) rather than decimal floats. Dynamics 365 Sales money fields accept decimal values. Loading an integer-cents value directly into Dynamics results in amounts 100x higher than intended. FlitStack AI detects the CASH field data type and currency storage convention during the discovery phase, applies division-by-100 transformation in the migration pipeline, and validates a sample of records against expected amount ranges before committing the full migration. This requires explicit handling per currency field and cannot be applied globally.

CASH datetime values lack timezone — Dynamics 365 requires UTC storage

CASH records commonly store dates and timestamps without timezone information, defaulting to the local server time at record creation. Dynamics 365 Sales stores all datetime values in UTC. When migrating records with CASH timestamps, FlitStack AI must normalize to UTC using the organization's known time zone (e.g., America/New_York) before loading into Dynamics ScheduledStart, CreatedOn, or custom datetime fields. Failure to normalize produces incorrect modified-on timestamps and activity sequences in Dynamics reports. The time zone must be confirmed with the client before migration because CASH does not embed time zone metadata in exported records.

Contact-company associations require Account to exist before Contact

Dynamics 365 Sales enforces that Contact.AccountId references a valid Account record. CASH allows contacts without a company assignment or with multiple company associations. FlitStack AI sequences the migration so all CASH companies migrate to Account records first, then contacts are loaded with AccountId populated from the resolved account. Contacts with no company in CASH land with AccountId blank. Contacts with multiple CASH companies are assigned to the primary (most-recently-modified) company and the additional associations are stored as Account Contact Relationships in Dynamics. This sequencing prevents foreign-key violations that would halt the migration mid-load.

Dynamics 365 file size limits apply to migrated attachments

Dynamics 365 Sales stores file attachments in SharePoint Online or OneDrive for Business, both subject to Microsoft-imposed file size limits (default 25MB per file in SharePoint). CASH attachments may exceed this limit. FlitStack AI measures each CASH attachment during the discovery phase, flags files over the SharePoint limit, and offers two paths: compress the file before re-upload, or split the attachment into chunks and reassemble in Dynamics. PDF and image files typically compress well; ZIP archives do not. This handling is documented in the pre-migration report before any file data moves.