Migrate from Planfix to Microsoft Dynamics 365 Sales

Planfix Contacts with a linked active Project or a deal-equivalent Task become Dynamics 365 Contacts attached to an Account. All other Contacts become Dynamics 365 Leads for qualification. We compute the split using Planfix's linked project reference and task status, and we preserve the original Planfix contact ID in a custom field planfix_original_id__c on both Lead and Contact for audit and reconciliation. Any Planfix contact without an email address is flagged as a partial record for the customer to enrich before migration.

Planfix Projects map to Dynamics 365 Account records with a custom account type value (e.g., ProjectAccount) to distinguish them from trading companies. The Planfix project description, start date, and end date migrate as custom fields. Project assignees migrate as Account Team members or CRM security roles depending on the Dynamics 365 edition. Projects without any linked Contacts are flagged as empty containers for the customer to decide whether to import as Accounts or archive before migration.

Planfix Tasks map to Dynamics 365 Task records. The Planfix task status maps to the Dynamics 365 StatusReason field, and the Planfix assignee maps to the Task's OwnerId via User email resolution. Custom fields on the Planfix task snapshot during schema discovery map to custom Task columns in Dataverse. Time logs (duration, date, user attribution) migrate as a JSON structure in a custom field time_log_entries__c unless the customer licenses Dynamics 365 Field Service, in which case they map to Time Entry records.

Planfix Workgroups (organizational units with shared permissions, capped at 100 on Plan X) map to Dynamics 365 Teams. Workgroup membership migrates as Team Membership records tied to the corresponding Dynamics 365 Users. Workgroup-level permissions do not have a direct Dynamics 365 equivalent; we document the permission matrix as a written guide for the customer's admin to recreate using CRM Security Roles and Field Security Profiles in the destination org.

Planfix time logs (from timers or manual entry against tasks) migrate as structured data. We preserve the duration in seconds, the date, and the user attribution for each time entry. In the standard Microsoft Dynamics 365 Sales migration scope, time log data is stored in a custom multi-line text field planfix_time_logs__c on the Task record in JSON format. If the customer adds Dynamics 365 Field Service, time logs map to the Bookable Resource time entries table with a direct relationship to the parent Task record.

Planfix Processes and Scripts are automation objects that reference Planfix-specific field IDs, action types, and trigger conditions. They cannot be exported or replayed in Microsoft Dynamics 365 Sales . We export the script configuration (trigger events, conditions, actions, and field references) as a written inventory document for the customer's admin to rebuild using Power Automate or Microsoft Dynamics 365 Sales Insights rules. Active processes are flagged in the migration report so that the customer does not lose a record of what was automated.

Planfix reports are built with the Planfix report builder and can be exported as CSV or XLSX. The underlying record data migrates to Dynamics 365; the report definitions themselves are not portable. We export the report data alongside the standard object migration and recommend rebuilding complex reports in Dynamics 365 using the Advanced Find, Power BI, or the Dynamics 365 out-of-the-box report designer post-migration.

Planfix document templates use XLSX/XLSM files with template variables to generate output documents. The template files migrate to the Dynamics 365 org's SharePoint document library or to the Dynamics 365 Document Templates feature. Template variable mappings (Planfix field names to Dynamics 365 field names) are workspace-specific and documented as a mapping guide for the customer's admin to reconfigure in the destination org. Mail merge setup requires Power Automate or a third-party document generation tool if the original template logic is complex.