Migrate from Flexie to Freshsales

Flexie Workers map to Freshsales Contacts. Name, email, phone, employment status, and availability windows migrate to standard Freshsales Contact fields. Workers who are not yet customers or prospects in a sales context may alternatively map to Freshsales Leads if the customer prefers to keep workforce records separate from active sales contacts. We preserve the original Flexie worker_id in a custom field flexie_worker_id__c on the destination record for cross-system auditing and future reconciliation.

Flexie Venues map to Freshsales Accounts. Venue name, address, and location-specific custom fields migrate to Account fields. For franchise or multi-location deployments, each Flexie Venue becomes a separate Freshsales Account, which allows territory assignment and account-level reporting in Freshsales. The original Flexie venue_id is preserved in a custom field flexie_venue_id__c.

Flexie Shifts are time-block records with a venue assignment and a worker reference. We offer two migration strategies during scoping: Shifts as Freshsales Deals (using the Shift name, start/end datetime, and associated Account and Contact links) or Shifts as Tasks with custom datetime fields. The choice depends on whether the customer wants shift data visible in the Freshsales pipeline view or as a task list on Contact or Account records. Closed or completed shifts become Deals with a Closed status; upcoming shifts become open Deals or scheduled Tasks.

Flexie Shift Assignments are the junction records linking a Worker to a Shift. We resolve the assignment by first creating the Contact (from Worker) and the Deal or Task (from Shift), then inserting the Task record with WhoId pointing to the Contact and WhatId pointing to the related Account. Assignment status (confirmed, pending, declined) and notes migrate as custom Task fields. Coverage gaps (unfilled shifts with no assigned worker) are flagged in a pre-migration report for the customer's admin to handle manually.

Flexie supports unlimited custom fields per Worker, and these vary by account. We extract the live schema via API during discovery, generate an explicit field map for each custom property, and pre-create matching custom fields in Freshsales before any record load. Custom picklist values are reviewed for character length limits in Freshsales. Any picklist value exceeding Freshsales limits is truncated or flagged for admin review.

Venue-level custom properties in Flexie migrate to custom fields on the corresponding Freshsales Account. These include location-specific operational settings, shift coverage thresholds, or compliance flags. We generate a field map during discovery and configure the destination custom fields before the Account migration phase.

Flexie Entity Forms serve as both data entry points and workflow triggers. They do not have a direct Freshsales equivalent because Freshsales does not have a standalone form builder for workforce records. We extract form definitions, field names, and submission records during discovery. Form submissions that represent worker or shift data migrate as Contact or Deal records. The form logic (triggers, conditions, automated actions) is documented in the written inventory for the customer's admin to rebuild using Freshsales Workflows.

Flexie Documents attached to Workers or Venues migrate as file attachments on the corresponding Freshsales Contact or Account record. We extract document metadata (filename, upload date, attached record type) and copy file links. Actual file hosting migration (moving files from Flexie's storage to Freshsales or a linked cloud storage) requires a separate file transfer step that we coordinate with the customer.

Flexie Workflows are platform-native automation sequences with triggers and actions specific to Flexie's workforce data model. They cannot be exported as reusable definitions and have no direct equivalent in Freshsales. We document every active Flexie Workflow during discovery, capturing its trigger conditions, action sequence, and the Flexie records it affects. The customer uses this inventory to rebuild equivalent automation logic in Freshsales Workflows after migration.