Migrate from Flexie to Nutshell

Flexie Workers map to Nutshell People. The worker's name, email, phone, and employment status migrate directly. Availability windows stored as custom properties on the Worker object map to custom fields on the Person record in Nutshell. Employment type (full-time, part-time, contractor) becomes a custom picklist field. We use the Worker email as the dedupe key during Person import. If the Worker email is blank, we fall back to a composite name-key for deduplication.

Flexie Venues map to Nutshell Accounts with a type-flag custom field (e.g. venue_type__c = 'QSR Location'). The venue address, city, state, and postal code map to the standard Account address fields. Venue-level operational settings that have no Account equivalent become custom fields on the Account. If the customer runs multi-location operations with distinct managers per venue, we preserve the manager assignment as a custom field or a linked Person role relationship in Nutshell.

Flexie Shifts have no direct Nutshell equivalent. We map each Shift to a Task record with a custom shift_type__c field set to 'Shift' and a custom venue_id__c reference pointing to the mapped Account. Shift start and end times map to ActivityDate and a custom shift_end__c datetime field. Shift status (open, filled, cancelled) becomes a custom picklist. If the customer has a large shift volume, we batch Tasks by week to avoid Nutshell's rate limits on large GET requests. Open shifts with no assigned worker require a decision during scoping: import as unattached Tasks or filter out pending admin review.

The Worker-to-Shift junction maps to a Task record where the WhoId is the migrated Person (Worker) and the WhatId is the associated Account (Venue). Assignment status, notes, and acceptance timestamp migrate to custom fields on the Task. If a Shift Assignment references a Worker who has not yet been imported, we hold the assignment record in a staging queue and resolve the WhoId reference after the Person is created. Coverage gaps—unfilled Shift Assignments—migrate as Task records with no WhoId and a custom coverage_gap__c flag set to true.

Flexie Entity Forms serve as data entry points and workflow triggers with no direct Nutshell equivalent. We extract form definitions during discovery, document the form fields and submission records as a written inventory, and map each form's captured data to existing or new custom fields on the relevant Nutshell Person or Account. The customer rebuilds form functionality using Nutshell's custom field input capabilities or a third-party form tool integrated via Zapier.

Documents attached to Workers, Shifts, or Venues in Flexie migrate as Note records in Nutshell linked via ContentDocumentLink to the parent Person or Account. The document name and a URL reference to the original Flexie file location migrate as the Note title and body. Actual file hosting (e.g. uploaded PDFs, images) must be moved separately via the file storage migration; we document the file inventory during discovery but do not handle binary file transfer as standard scope.

Flexie allows unlimited custom fields per object, and these are not centrally documented. We extract the live Worker schema via API during discovery and generate an explicit field map before any load. Custom picklist values must be reviewed for Nutshell's length limits (255 characters per field). Multi-select picklists in Flexie map to Nutshell custom fields with a pipe-delimited string value, or we recommend splitting to multiple boolean fields if the customer prefers normalized storage.

Venue-level custom fields (operational settings, location-specific attributes) map to Account custom fields in Nutshell. We flag any venue-specific fields that reference other Worker records, as these require the Worker import to complete first before the lookup reference can be resolved. Custom date fields on Venues map to Nutshell custom date fields without transformation.

Flexie Workflows are platform-native automation sequences with triggers and actions that have no direct Nutshell equivalent. We do not migrate Workflows as code. We document every active Flexie Workflow with its trigger conditions, action steps, and object dependencies during discovery, and deliver a written workflow inventory for the customer's admin to rebuild in their chosen automation tool (Zapier, Make, or Nutshell's native activity logging). This is the primary reason the migration includes a documentation handoff rather than an automated workflow transfer.