Migrate from Planfix to Salesforce Sales Cloud

Planfix Contact records map directly to Salesforce Contact. Each Contact in Planfix carries a profile card with contact info, linked tasks, files, and a history log. We export contact records including all custom properties and relationship links. AccountId on the Salesforce Contact is resolved by matching the Contact's linked Company or Project in Planfix to the pre-migrated Account record. The Planfix contact's email address serves as the dedupe key during import.

Planfix Company records map to Salesforce Account. The Company name becomes Account Name, and any website or domain field maps to Account Website. Account is loaded before Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. Companies without a billing or address relationship map to the standard billing address block.

Planfix Projects present a split decision: client-facing Projects with a billable relationship map to Salesforce Account, while internal initiative Projects that do not represent customer organizations may map to a custom Project__c object. We define the split rule during scoping based on whether the Project record carries client contact links and billing fields. Project templates and task structures are preserved as task hierarchies linked to the parent Account or Project__c record.

Planfix Tasks are the core record type and do not have a single Salesforce equivalent. Project execution tasks map to Salesforce Task with WhatId pointing to the related Account or Project__c. Customer-facing support tasks that represent issue tracking map to Salesforce Case, with Case Record Types and Status values configured to match the source Planfix task status matrix. The split is defined during scoping by examining the task's custom status field values and linked contact relationships.

Planfix Workgroups (up to 100 on Plan X) group users and set shared permissions. We map workgroup memberships and roles to Salesforce Public Groups, translating Planfix workgroup names and member lists into Salesforce group structure. Individual user records map to Salesforce User via email match. Workgroup-level permission sets may require the customer's Salesforce admin to create matching Permission Sets post-migration.

Planfix custom fields vary per workspace with different names, types, and IDs. We snapshot the field schema from the Planfix API before mapping any record, capturing field type (text, number, date, dropdown, checkbox, file). Each Planfix custom field maps to a typed Salesforce custom field with a __c suffix. Dropdown fields map to Salesforce picklists with values migrated as picklist values; checkbox fields map to Salesforce checkboxes. Custom field data is loaded after the field schema is deployed to Salesforce to prevent type mismatch errors.

Time logged against Planfix tasks via timers or manual entry is exported as a structured field and mapped to a custom Duration__c field (number of minutes) on the corresponding Salesforce Task or Case record. We preserve the duration, date, and user attribution for each time entry. If the customer's Planfix instance uses time log categories, these map to a custom picklist on the duration field.

Planfix Planners are calendar-based views of tasks with saved filters, groupings, and date ranges. The underlying task data migrates to Salesforce Task and Case; the saved Planner configurations are user-specific and cannot be preserved as data. We deliver a written inventory of Planner view configurations for the customer's admin to rebuild as Salesforce List Views, Report types, or Lightning Calendar components.

Planfix Reports are built with the report builder and exportable as CSV or XLSX. Saved report definitions are not directly portable to Salesforce. We export the underlying data from Planfix Reports and deliver a written inventory of report configurations with their filters, groupings, and calculated fields, recommending Salesforce Report types and custom report folders as the rebuild path.

Planfix Processes and Scripts are event-driven automation objects that reference Planfix-specific field IDs and action types. They are tightly coupled to Planfix's internal execution engine and cannot be reliably exported or replayed in Salesforce. We export script configurations as written documentation describing the trigger, conditions, actions, and field references for the customer's admin or implementation partner to rebuild in Salesforce Flow.

Planfix Document Templates use XLSX/XLSM files with template variables. The template files themselves can be exported; variable mappings are workspace-specific and may require field remapping. We export template files as ContentDocument records in Salesforce. Variable substitution logic (how Planfix resolves template variables) does not migrate and requires the customer's admin to rebuild in Salesforce Document Generation or a third-party document merge tool.

Planfix Whiteboard content stores block-based diagrams with no documented export or API access. These records are flagged as non-migratable before the migration begins. We offer to capture screenshots of Whiteboard content as a visual record for the customer, but the underlying diagram data cannot be structured for import into Salesforce. This is disclosed in the pre-migration scope document and requires customer sign-off.