Migrate from Timefold to monday CRM

Timefold tenants map directly to the monday CRM account at a 1:1 ratio. All members associated with the source tenant are migrated as monday CRM users invited to the same account. Email addresses serve as the join key for identity preservation, ensuring that owner resolution in item assignments references the correct monday user identities that originated from the Timefold member records.

Timefold members migrate as monday CRM users using email as the primary join key for resolving worker and owner assignments across boards. Members whose Timefold records contain email addresses not yet registered in monday CRM are flagged as provisioning-required before migration execution to prevent orphaned references on shift and visit items.

Each Timefold planning model—such as field-service-routing, employee-shift-scheduling, or pick-up-and-delivery—becomes a separate monday CRM board. The board name derives directly from the model name. The board's default group receives the initial migration batch of items; subsequent groups map to Timefold subgroups, sub-models, or solver-generated partitions within the original model structure.

Timefold workers and employees migrate as items within a dedicated monday CRM team-operations board. Worker attributes such as skills, certifications, and availability windows map to corresponding monday column types including multi-select for skills, date columns for availability, and timeline columns for working hours. The original Timefold worker ID is preserved as a read-only text column for traceability and cross-reference during validation.

Timefold skill definitions become a monday CRM multi-select column on the worker board. Each distinct skill value in Timefold creates a corresponding option in the column. Skill requirements on visits or jobs map to matching multi-select columns on those boards, with option values aligned across boards to enable filtering and matching functionality.

Timefold locations with geographic coordinates migrate as items in a monday CRM locations board and simultaneously as Location column values on visit or job items. Address fields from Timefold parse into monday's structured address sub-fields including city, street, state, and zip code, enabling both human-readable address display and geospatial functionality through the Location column's coordinate data.

Timefold shift records become items in a monday CRM shifts board. Start and end times map to monday date and timeline columns. The assigned worker reference resolves to the corresponding monday item via email-based owner matching. Shift status values (published, draft, cancelled) map to a monday status column with matching option labels.

Timefold visits and jobs—the core planning entities in field-service-routing models—migrate as items in a monday CRM visits board. Priority, time window, required skills, and travel-time requirements map to corresponding monday column types. The planning entity's planning-variable assignments (which worker, which route) store as person and location column references that link back to the migrated worker items and location items.

Timefold route plans—the optimized sequence of visits assigned by the solver—map to monday CRM groups within the visits board. Each group represents a single route. The group's items (visits) are ordered by the solver's visit sequence number stored as a numeric column. Route-level metadata such as total distance and total time becomes group-level columns on the monday group header.

Timefold solver scores (hard, medium, soft constraint scores) have no monday CRM equivalent. FlitStack stores the final solver score as read-only number and text columns on the affected board items for audit and reference. Solver scores do not trigger any automation in monday CRM and will not recalculate if monday users manually modify assigned values.

Files attached to Timefold records—including planning documents, constraint definition exports, route maps, and reference PDFs—are downloaded from Timefold storage and re-uploaded to the corresponding monday CRM items using monday's native file storage. File size limits and supported formats (PDF, images, spreadsheets) follow monday's upload constraints as documented for your specific monday plan tier.

Timefold constraint definitions and solver recipes are solver-engine configurations expressed in DRL rules or Constraint Streams with no monday CRM counterpart. FlitStack exports these recipe definitions as JSON documents and constraint-rule plain-text files for your Monday admin to use as a functional specification when rebuilding equivalent automation rules or conditional logic in monday's recipe syntax.

Timefold API integrations with external ERPs, telephony platforms, or routing systems have no monday CRM equivalent and cannot be migrated directly. FlitStack documents each active integration endpoint identified during discovery—including webhook URLs, authentication methods, payload structures, and data flow direction—as a configuration reference document for your team to use when rebuilding connections as monday integrations or native API calls post-migration.