Migrate from Column Case Management to Microsoft Dynamics 365 Sales

Column Cases map 1:1 to Dynamics 365 Incidents. The Case title becomes the Incident Title, Case ID is stored as Source_Case_Number__c, and case status maps to Incident State/StatusCode via value mapping. Column-created and closed timestamps are preserved in custom datetime fields.

Each Column Subject record with type 'Person' migrates to a Dynamics Contact. Subject first name, last name, email, phone, and address fields map directly. Unmatched subjects are flagged before migration — your team assigns a fallback account or imports as inactive contacts.

Column Subjects with type 'Organization' migrate to Dynamics Accounts. Organization name maps to Account.Name, domain to Website, and industry to Industry pick-list via value mapping. Parent-subject hierarchies map to Account.ParentAccountId. Where no industry match exists in Dynamics option set, we apply a default 'Other' value for continuity, and your admin updates it post-migration. Organizational address fields map to Address1 composite or individual address components on the Account record.

Column allows N Subjects per Case. Dynamics Incidents require a single primary customer (Contact or Account). We map the primary subject as Incident.CustomerId and store additional subject references in a custom multi-select option set (Additional_Subjects__c) for investigative continuity. Cases with zero subjects are assigned a default 'Unassigned' Account placeholder so every Incident maintains referential integrity with a valid CustomerId lookup.

Evidence records require a custom Dynamics entity (flitstack_Evidence__c) or SharePoint document library linked to the Incident. Chain-of-custody fields (collected date, collected by, storage location) migrate as custom fields on the evidence entity. File attachments re-upload to SharePoint and linked via a URL field.

Column documents attached to cases migrate to SharePoint document libraries associated with the Incident. Small inline documents or images are stored as Dynamics Notes attachments (max 5MB per note). We preserve the original document name, upload date, and uploaded-by user reference.

Column case owner usernames are matched by email to Dynamics SystemUser records. Unmatched owners are flagged pre-migration — your admin either invites them to Dynamics or assigns their cases to a fallback owner. Ownership is resolved before Incident records are written so every record lands with a valid OwnerId.

Column's custom fields on Cases (text, number, date, pick-list) translate to Dynamics custom fields with 'new_' schema prefix. Field type is preserved — pick-lists become option sets, dates stay datetime. Required-field constraints must be set in Dynamics before migration; we handle the data transform.

Column case status values (Open, In Review, Closed, etc.) map to Dynamics Incident StateCode and StatusCode via value-by-value mapping. Probability and resolved-flag are re-applied based on Dynamics status values. Stage-entered timestamps are preserved in a custom datetime field for audit continuity.

Column priority (Critical, High, Medium, Low) maps to Dynamics PriorityCode option set values. The mapping is 1:1 — Critical maps to High Priority in Dynamics, High maps to Normal, etc. Your admin confirms the value map before the migration run commits.

Column workflows do not have a Dynamics equivalent. We export workflow definitions (trigger conditions, step sequences, assignee rules) as JSON/PDF documentation. Your Dynamics admin rebuilds them using Power Automate or Dynamics process flows, referencing the exported definitions as the rebuild spec.

Column reports and dashboards are not transferable. The underlying data migrates to Dynamics, so Power BI reports can be rebuilt against the same data. FlitStack provides a data dictionary mapping Column fields to Dynamics fields so Power BI authors can build equivalent visualizations without a data migration round-trip.

File attachments from Column migrate to SharePoint document libraries associated with the target Incident. Files under 5MB are stored as Dynamics Note attachments. File name, size, upload timestamp, and uploaded-by user are preserved. Inline images in notes are downloaded and re-hosted in SharePoint.