Migrate from Timefold to Twenty CRM

Timefold's Shift entity (employee-to-shift assignments, start/end times, location) migrates as a Twenty custom object with fields for shiftName, startTime, endTime, locationId, and assignedEmployee. Twenty's custom object creation via Settings → Data Model must happen before CSV import or API load.

Timefold Field Service Routing's Visit entity (customer location, time window, required skills, duration) maps to a Twenty custom object. The visit's time window dates become startDate and endDate fields; required skills become a multi-select field or linked Skills custom object.

Timefold routing models' Vehicle entity (capacity, skills, startLocation) maps to a Twenty custom object. Vehicle capacity and skill requirements become number and multi-select fields respectively. Routes assigned to this vehicle in Timefold's solution become linked Route records. If your routing model includes multi-day routes with intermediate stops, the route hierarchy is preserved as nested relation fields on the Vehicle record.

When Timefold's employee roster needs to link to a CRM contact model, the Employee entity maps to Twenty's People object. Standard fields: name, email, phone, jobTitle. Employee skills stored in Timefold become a multi-select custom field on the People record.

Timefold planning tasks (the work items being assigned to employees/shifts) map to Twenty's standard Tasks object. The Twenty Tasks object supports dueDate, assignee (linked to People), status, and body — matching the structure of a generic planning task. Task dependencies from Timefold become predecessor-link custom fields on the Twenty Tasks record.

Timefold location records (addresses, coordinates for routing) can map to Twenty Companies for physical service locations. The Company object captures address, city, country, and domain. Locations used in Visit routing become Company records with address fields populated from Timefold's location data. GPS coordinates from Timefold are stored in a custom lat/long field on the Company record for map integration.

Timefold's planning variable assigning an Employee to a Shift becomes a relation field (assignedEmployee) on the Shift custom object in Twenty. This is a lookup to the People record representing the employee, resolving the foreign key by email match. If an employee record does not yet exist in Twenty, FlitStack creates a stub People record to preserve the assignment relationship.

Timefold's vehicle assignment for a Visit (which vehicle serves which visit) becomes a VehicleId lookup field on the Visit custom object. The vehicle must exist as a Vehicle custom object record before the Visit assignment can reference it. This ensures referential integrity during import and prevents orphan lookups on the Twenty side.

Timefold's score output (e.g., '0hard/-257medium/-6119520soft') has no native equivalent in Twenty. We store it as a text field (Score__c) on each planning entity for historical reference. Teams using score to evaluate schedule quality see it as metadata on the entity record. Score__c enables audit and compliance review but requires spreadsheet export for trend analysis.

Timefold's constraint definitions (hard rules like skill matching, soft rules like travel time minimization) cannot auto-enforce in Twenty. We export them as structured JSON into a ConstraintReference custom object — name, type (hard/medium/soft), definition text, and weight — serving as a manual-rebuild guide for Twenty workflow configuration.

Each Timefold optimization run (solving a planning problem to produce a schedule) maps to a ScheduleRun custom object in Twenty. Fields: runDate, modelName, entityCount, scoreValue, and a link to the generated Shift/Visit/Vehicle assignments. This gives an audit trail of what the optimizer produced historically.

Timefold domain models with custom entity classes (beyond Shift/Visit/Vehicle) map 1:1 to Twenty custom objects. Each entity property becomes a field in Twenty's data model. Relationships between custom entities in Timefold become relation fields or junction objects in Twenty based on cardinality.