Migrate from Flexie to Microsoft Dynamics 365 Sales

Flexie Workers map to Dynamics 365 Sales Contacts. First name, last name, email, phone, employment status, and hire date transfer directly. Availability windows (days and hours) are not a native Dynamics field and require a custom multi-select or text field that we configure during schema setup. Worker status (active, on leave, terminated) maps to Contact Status with a custom field for Flexie-specific status values. If the customer uses Flexie to track candidate pools separately from active workers, we distinguish between Contacts (active workers) and Leads (prospective workers) during the split.

Flexie Venues map to Dynamics 365 Sales Accounts. Name, address, city, state, postal code, and venue type transfer directly. For franchise or multi-location operators, we implement an Account hierarchy where the parent franchise Account holds corporate-level data and each Venue Account is a child record. Venue-level custom fields (capacity, shift count, manager assignment) require pre-created custom fields in Dynamics 365 before migration.

Flexie Shifts do not have a native Dynamics 365 Sales equivalent. We pre-create a custom entity flexie_shift__c in the destination Dataverse environment with fields for shift_start__c (DateTime), shift_end__c (DateTime), venue__c (Lookup to Account), assigned_worker__c (Lookup to Contact), shift_status__c (Optionset: open, filled, cancelled), and shift_notes__c (Text). This custom entity is configured before migration and registered with the customer's Dynamics 365 admin for long-term access.

Shift Assignments in Flexie are the junction between Workers and Shifts. We resolve the assignment at migration time by inserting the flexie_shift__c record with both venue__c (Account) and assigned_worker__c (Contact) lookups populated from the Flexie shift record. Coverage gaps (unfilled shifts where no worker is assigned) are inserted as flexie_shift__c records with a null assigned_worker__c and shift_status__c = open. We flag open shifts for review before final import because Dynamics 365 does not natively surface unfilled shift records.

Flexie supports unlimited custom fields per Worker record, and these vary by account. We extract the live schema via API during discovery, map each custom property to a typed Dynamics 365 custom field (Text, Number, DateTime, Picklist, or Boolean) on the Contact object, and generate a field map before any data load. Custom picklist values are reviewed for Dynamics 365 picklist length limits (50 characters per value). Fields exceeding the limit are truncated with a flag in the migration report.

Flexie venue-level custom fields map to custom fields on the Account object in Dynamics 365. We follow the same field extraction and type-mapping process used for Workers, generating a field map during discovery and pre-creating custom fields in the destination environment before migration. Venue operational settings (manager ID, shift approval required, overtime rules) are mapped to custom fields on the Account record.

Flexie Entity Forms serve as data entry points and workflow triggers. These do not have a direct Dynamics 365 equivalent because Dynamics 365 Sales uses model-driven Power Apps forms as the standard record entry interface. We document every active Entity Form with its field layout, submission logic, and any associated workflow triggers so the customer's admin can reproduce the data entry experience using Power Apps or Power Pages post-migration.

Documents attached to Flexie Workers, Venues, or Shifts migrate as file metadata (filename, file type, upload date, Flexie record association) documented in a migration manifest. We extract the document URLs from Flexie and map them to a SharePoint document library linked to the corresponding Account or Contact record in Dynamics 365. Actual file hosting (migrating binary document files) is handled separately as a document migration task because it requires SharePoint or OneDrive API access beyond standard CRM migration scope.