Migrate from Planado to Microsoft Dynamics 365 Sales

Planado Clients map to Dynamics 365 Accounts. Primary address from Planado client record moves to Account.Address1 fields. Parent-child site relationships in Planado map to Account.ParentAccountId hierarchy in Dynamics 365. FlitStack preserves the full address record including street, city, state, postal code, and country in separate Address1 fields for consistent geocoding and territory segmentation downstream.

Planado Sites (physical locations per client) do not have a direct Dynamics 365 equivalent. FlitStack maps primary sites as Account records with site-type naming convention; additional sites move to a custom Site custom table or stored as address records on the parent Account.

Planado employees who are licensed Dynamics 365 Sales users migrate as User records resolved by email match against your Entra ID tenant. Non-user employees including subcontractors, part-time staff, and seasonal workers migrate as Contacts linked to their primary Account for territory alignment, reference lookup, and scheduling purposes. OwnerId lookups on TaskHistory resolve during this split mapping phase.

Planado Tasks (field jobs) do not map to Dynamics 365 Opportunities because Opportunities track revenue decisions, not service completions. Completed tasks migrate as records in a custom TaskHistory custom table keyed to Account, preserving job type, status, assignee, and completion timestamps.

Planado task status values (Pending, In Progress, Completed, Cancelled) map to a custom picklist on the TaskHistory custom table in Dynamics 365. Each status code translates value-by-value with consistent labeling. Cancelled tasks migrate with a cancelled flag for historical completeness, ensuring your team can filter and report on cancelled work without data loss.

Planado checklist items per task migrate as child records in a custom ChecklistItem custom table linked to TaskHistory. Item completion status, response values, and timestamps preserve the operational audit trail. Static checklists also export as PDF attachments to the parent Account.

Planado route assignments and scheduling rules have no Dynamics 365 Sales equivalent and do not migrate programmatically. FlitStack exports route definitions as a reference JSON file your Power Automate team uses to rebuild scheduling logic in Dynamics 365 Field Service, preserving the configuration intent for manual reimplementation.

Planado GPS visit logs carry operational context but have no standard Dynamics 365 Sales equivalent. FlitStack preserves these as entries in a custom FieldVisitLog table linked to Account and TaskHistory for reference — these records serve as audit trail data, not as native Dynamics 365 activities, and require custom Power BI reports for visualization.

Planado report templates use Planado-specific formatting with no direct Dynamics 365 equivalent. FlitStack exports report definition metadata as a rebuild reference. Power BI dashboards built on migrated TaskHistory and ChecklistItem data provide equivalent reporting within Dynamics 365 using standard Power BI Desktop authoring tools.

Planado custom fields migrate to matching custom fields on the destination table in Dynamics 365. FlitStack creates the custom fields in your Dynamics 365 environment during the pre-migration schema setup phase. Field type mapping (text, number, picklist) follows Dataverse type conventions for compatibility with Power Apps and Power Automate flows.