Migrate from Timefold to Salesforce Sales Cloud

Timefold Workers map to Salesforce Contacts if they are external contractors or field staff without Salesforce login. Workers who are internal employees and need CRM access map to Salesforce Users matched by email. Skill certifications on the Worker become a custom multi-select picklist on the Contact record. Unmatched workers are flagged before migration so you can decide whether to create Contact records or invite them as Users.

Timefold Visits map to Salesforce Tasks (for checklist-style assignments) or Events (for calendar-block appointments). Original start time, end time, and time window from Timefold are preserved as Task/Event fields. Visit status (scheduled, in-progress, completed, pinned) maps to the Task Status or Event status fields. Required skills on a visit are stored as a custom text field for reference by your scheduling admin.

Timefold Visits map to Salesforce Tasks (for checklist-style assignments) or Events (for calendar-block appointments). Original start time, end time, and time window from Timefold are preserved as Task/Event fields. Visit status (scheduled, in-progress, completed, pinned) maps to the Task Status or Event status fields. Required skills on a visit are stored as a custom text field for reference by your scheduling admin.

Timefold route plans (from the Field Service Routing model) do not have a Salesforce standard equivalent. FlitStack creates a custom Route__c object storing route name, vehicle ID, driver worker reference, total planned distance, and optimization score. Each visit on the route becomes a child Visit__c record linked to Route__c, preserving the sequence order and travel time between stops.

Timefold visit locations include a customer reference (name, address, contact). These map to Salesforce Accounts — either the Account Name for business locations or a synthesized name for residential sites. The street address, city, and geocoordinates from Timefold map to the Account billing address fields. If the location has an associated Timefold contact, a corresponding Contact record is linked via AccountId.

Timefold Employee Shift Scheduling shifts map to Salesforce Events (for calendar display) or a custom Shift__c object for reporting. Each shift carries worker reference, start datetime, end datetime, and required skills. Salesforce Events do not natively support skill requirements — these are stored as a custom field on the Event or as a separate Shift__c custom object depending on whether you need reporting on shift coverage by skill.

Timefold skills (e.g., HVAC certified, CDL licensed, bilingual) are referenced on Workers and Visits but are not first-class objects in Salesforce. FlitStack creates a Skill__c custom object and a junction object ContactSkill__c linking Skills to Contacts. This allows your admin to run reports on skill coverage per Account or territory.

Timefold planning solutions carry a hard/medium/soft score (e.g., -257medium/-6119520soft) indicating constraint satisfaction. This score has no Salesforce equivalent. FlitStack creates a PlanningRun__c custom object that records the run date, the score, and a reference to the resulting schedule — for audit and historical comparison of optimization quality over time.

Timefold's multi-tenant platform model means a single Timefold installation can have multiple tenants with separate member lists and models. If your Timefold instance has multiple tenants, FlitStack maps each tenant to a Salesforce Account (for customer-facing tenants) or a custom TimefoldTenant__c label on the User for internal tenants. This prevents data from different tenants mixing in a shared Salesforce org.

Timefold visit attachments (photos, signatures, job completion forms) are downloaded and re-uploaded to Salesforce Files linked to the corresponding Task or Visit__c record. File size limits apply — Salesforce Files default to 25MB per file. Files exceeding this are chunked or linked by URL reference.

Timefold constraint definitions (written in Java/Kotlin with @ConstraintProvider annotations) are code artifacts with no Salesforce equivalent. FlitStack exports constraint logic as a structured JSON reference document and a written requirements summary so your Salesforce admin or a Flow developer can configure equivalent Validation Rules or Flow decisions in Salesforce.

Timefold optimization settings (nearby selection, partitioned search, multithreaded solving) are platform configuration, not data. These are documented in the export so your scheduling administrator understands what problem characteristics (shift length, visit frequency, vehicle capacity) the Timefold model was tuned for when rebuilding in Salesforce or an AppExchange scheduling tool.