Migrate from Timefold to Microsoft Dynamics 365 Sales

Constraint configurations have no Dataverse native equivalent and must be rebuilt

Timefold's constraint definitions — written in the PlanningAI DSL or configured via score analysis — encode business rules like skill-matching requirements, travel time caps, and capacity minimums that produce hard, medium, and soft scores per plan run. Microsoft Dynamics 365 Sales has no native constraint-satisfaction engine. FlitStack AI exports the full constraint configuration as a structured JSON file so your Dynamics administrator can rebuild equivalent logic using Power Automate conditions, Dataverse business rules, or custom plugin code. Skipping this step leaves Dynamics with static scheduling records but no optimization capability.

Skill-to-technician matching requires a custom junction table in Dataverse

Timefold models skill requirements on visits and skill certifications on technicians as first-class planning entity properties. Dynamics 365 Sales System User records have no native skill field. We create a Skill__c custom table and a User_Skill__c junction table with a many-to-many relationship so that visit routing rules can reference skill compliance. This requires Dynamics 365 Sales Enterprise licensing — the Professional tier caps custom tables at 15 and may not accommodate the full scheduling schema.

Dataverse API request quotas impose migration throughput limits

Dynamics 365 Sales (built on Dataverse) enforces per-user/per-environment API request limits that vary by license tier. Timefold's REST API can export large planning datasets quickly, but ingestion into Dynamics 365 Sales must respect these quotas to avoid throttling. FlitStack AI uses Dataverse batch operations and pagination strategies tuned to the target environment's allocation, with retry logic for 429 responses. Teams with datasets exceeding 500,000 visit records should plan multi-day ingestion windows.

Visit time windows require custom date/time field handling for timezone accuracy

Timefold stores visit start and end times in UTC or a configured timezone on the planning problem. Dynamics 365 Sales Task ScheduledStart and ScheduledEnd fields store datetime values that are displayed in the user's local time zone via UI settings. FlitStack AI preserves the original UTC timestamps and stores a Timezone_Original__c reference field so scheduling reports can display accurate window data without double-converting during daylight saving transitions. If your organization uses multiple time zones across service territories, the Timezone_Original__c field allows Power BI reports to recalculate windows against the correct regional schedule, preserving the intended arrival slots for each location.

Field Service licensing is required for Bookable Resource Booking shift records

The most semantically correct mapping for Timefold shifts is Dynamics 365 Field Service's Bookable Resource Booking entity — it models resource allocation to time blocks with requirement matching. However, Field Service requires a separate license beyond Sales Professional or Enterprise. Teams without Field Service licensed must use Outlook Calendar Events on System Users as a proxy, which lacks the requirement-linking capability of Bookable Resources. This proxy approach reduces reporting granularity for capacity planning and requires custom fields or manual tracking to simulate the requirement constraints that Bookable Resources handle natively.