Migrate from Flexie to Salesforce Sales Cloud

Flexie Workers map directly to Salesforce Contact records. The Worker's name fields map to FirstName and LastName on Contact. Contact phone, email, and address fields migrate directly. Availability windows from Flexie (days and hours a worker is available) map to custom fields availability_start__c and availability_end__c or a custom Availability object if the customer tracks granular availability patterns. Employment status (active, inactive, suspended) maps to Contact.Status__c or the standard Contact.Active__c field if configured.

Flexie Venues map to Salesforce Account records. The venue name becomes Account.Name, and the venue address migrates to the standard BillingAddress fields on Account. If the Flexie venue tracks industry type or venue category (QSR, hospitality, retail), those values map to Account.Industry or a custom venue_category__c picklist. Account is created before any Contact import so that the AccountId lookup on Contact is satisfied at migration time.

Flexie allows Workers to be assigned to one or more Venues. This many-to-many relationship maps to Salesforce AccountContactRelation, which links the Contact (from Worker) to the Account (from Venue). We extract the Worker-Venue assignments during discovery, create AccountContactRelation records during migration, and preserve any role or permission level from Flexie in the Role field on AccountContactRelation.

Flexie Shifts do not have a direct Salesforce standard object equivalent. We create a custom Shift__c object on the destination org with fields for shift_date__c (date), start_time__c (time), end_time__c (time), status__c (open, filled, cancelled), and a lookup to the assigned Contact. The custom object is deployed via metadata API into a Sandbox first for validation before production migration.

Flexie Shift Assignments are the junction between Workers and Shifts. We create a custom ShiftAssignment__c object with a Master-Detail relationship to Shift__c (or a lookup) and a Lookup to Contact. The assignment status (confirmed, pending, declined, no-show) and any assignment notes migrate to status__c and notes__c on the assignment record. Coverage gaps (unfilled shifts with no assignment) are flagged during migration and reported separately for the customer's scheduling team to address.

If the customer uses Flexie Shifts to track operational capacity or service revenue, Shifts can also map to Salesforce Opportunity records with a custom record type Shift Capacity. Shift revenue, headcount filled, and coverage percentage become custom Opportunity fields for reporting. This is an optional configuration discussed during scoping; the standard mapping remains the custom Shift__c object.

Flexie Entity Forms serve as data entry points and workflow triggers with no direct Salesforce equivalent. Form submission records migrate to a custom EntityFormSubmission__c object with fields for form_name__c, submitted_by__c (Contact lookup), submission_date__c, and the form field values stored as custom fields or in a serialized JSON field. Form definitions (field list, validation rules, triggers) are documented for rebuild in Salesforce as screen Flows with a related custom object.

Flexie Workflows are automation sequences built on triggers and actions. These do not migrate 1:1 to Salesforce Flow because the trigger models, action types, and delay mechanisms differ. We document every active Flexie Workflow with its trigger (form submission, shift event, date-based), conditions, actions, and a recommended Salesforce Flow equivalent. The customer's admin rebuilds workflows post-migration; this is a separate engagement scope.

Flexie Documents attached to Workers, Shifts, or Venues migrate as Salesforce ContentDocument records. We extract the document metadata (filename, type, upload date, attached entity) and recreate the ContentVersion record with the file binary if accessible. If the document host in Flexie is a link rather than a hosted file, we store the URL in a custom External_Document_Link__c field on the ContentDocument.

Flexie allows unlimited custom fields per Worker. Each custom property is mapped to a Salesforce custom field on Contact with the appropriate type (text, picklist, date, number, checkbox). Picklist values are reviewed against Salesforce picklist length limits (40 characters per value) and remapped if needed. Custom properties unique to the customer's Flexie account are documented with their API names during discovery.

Flexie Venue custom fields (operational settings, location-specific configurations) map to custom fields on Salesforce Account. We extract the live schema via Flexie API during discovery and generate an explicit field map. Venue-specific operational flags and settings that have no Salesforce standard equivalent become custom Account fields for the customer to configure.

Any Flexie custom fields on Shift records map to custom fields on the custom Shift__c object. If the customer uses Shift-level custom fields for scheduling type, department, or coverage notes, we create equivalent custom fields on the Shift__c object during schema design.

Flexie tracks shift managers and venue administrators. We resolve these by email against the Salesforce destination org's User table. Any Flexie owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.