Migrate from Timefold to Zoho CRM

Timefold planning problems contain problem facts (employees, locations, demand) submitted via POST /route-plans. We map these as records in a Zoho CRM custom module with fields for model type, input timestamp, and the raw JSON payload stored as a long-text field for audit traceability.

Timefold returns optimized output datasets via the solve API — assigned shifts, route sequences, technician assignments. We map these as Zoho custom module records with lookup links to the corresponding Planning_Problem__c record so every solution traces back to its input problem.

Timefold encodes hard, medium, and soft constraints in DRL files or Constraint Streams. We extract constraint names and weight categories, storing them as records in a custom module so the business context of each constraint is documented in Zoho CRM for admin reference.

Timefold produces composite scores like '0hard/-257medium/-6119520soft'. We parse these into three separate custom Number fields on the Planning_Solution__c record so your Zoho reports can filter and sort by score component across all historical optimization runs. Each field stores an integer representing constraint violations, penalty magnitude, or preference deviation, enabling trend analysis and alerting on score degradation.

Timefold planning entities (shift assignments, route visits, delivery jobs) have planning variables that change during solving. We create a Zoho custom module for each entity type with fields for the entity ID, type label, and the assigned resource — linked to the parent Planning_Solution__c.

Timefold problem facts — the resources that get assigned during solving — map directly to Zoho CRM Contacts. We preserve original resource IDs as a custom field for traceability and link each Contact to its parent Planning_Problem__c record via a lookup relationship.

Timefold locations and service sites map to Zoho CRM Accounts. We use the Account Name for site identifiers and store the original Timefold location ID in a custom field. Parent-child site hierarchies map to Zoho's Parent Account field. This mapping preserves geographic context and supports location-based reporting within Zoho Analytics.

Timefold multi-tenant installations have Members scoped to Tenants. We map each Timefold Tenant to a Zoho CRM Role configuration and document the member-to-role assignments as a reference sheet for your Zoho admin to implement after migration. The reference sheet includes role names, permissions, and data-sharing rules required for accurate access control.

Timefold pre-built models (field service routing, employee shift scheduling, vehicle routing) are configured per organization. We store model names, versions, and solver settings in a Zoho custom module so the configuration state is queryable and versioned in Zoho CRM. This enables your team to audit model changes and replicate solver behavior in Zoho's automation tools.

Timefold Enterprise and Plus editions produce score analyses with per-constraint breakdowns. We store these as custom records linked to the parent Planning_Solution__c, with fields for constraint name, weight, and violation magnitude — enabling Zoho dashboards to visualize which constraints drive score degradation.

Timefold's Model SDK connects planning models to tenant-specific data sources. We export SDK configuration references as custom text fields in Zoho CRM — your integration team uses these as connection parameters when rebuilding API integrations in Zoho's Deluge environment. These parameters include endpoint URLs, authentication tokens, and data format specifications needed for stable connectivity.

Timefold supports uploading CSV or JSON input files for planning problems. We re-attach these files to the corresponding Planning_Problem__c record in Zoho CRM using Zoho's native file attachment mechanism, preserving the original filename and upload timestamp. This ensures file provenance is maintained and allows users to reference source data directly within Zoho's interface.