Migrate from Planisware Enterprise to Trello

Planisware Portfolios contain member projects with portfolio-level budgets and strategic alignment attributes. Trello has no native portfolio concept above the board level. We split each Planisware Portfolio into a Trello Workspace (for organization-level grouping) or a Board group, with member projects mapped to individual Boards. Portfolio budget totals and strategic alignment metadata are documented in a separate gap-analysis spreadsheet that the customer uses to decide whether to track totals in a connected Google Sheet or recreate them in Trello using a reporting Power-Up.

Planisware Projects map directly to Trello Boards. We extract the project name, description, start and end dates, status, owner assignment, and custom properties. The Planisware project status (Active, On Hold, Closed) maps to Trello Board visibility and the primary List name. Owner assignment migrates as a Board member with Admin or Member role. Projects with sub-projects are split into a parent Board and child Boards linked via a cross-board card reference documented during scoping.

Planisware Activities map to Trello Cards. We extract task name, description, planned and actual start/end dates, status, priority, and assignees. Planisware task hierarchy (parent and child activities) is preserved by creating Trello Cards for each activity and using card links or checklist nesting to represent the parent-child relationship, since Trello Cards do not have a native sub-task hierarchy above checklist items. Tasks without assignees in Planisware are created as unassigned Cards with a label noting the original owner was not found.

Planisware Resources include capacity percentages, skill profiles, and cost rates used in resource forecasting. Trello has no resource management capability beyond assigning a Card to a Board member. We extract resource names and migrate them as Board Members with Member role. Allocation percentages and skill profiles cannot be represented natively in Trello; we document these as a Resource Gap Report listing each resource's Planisware allocation per project so the customer can recreate a capacity view in a connected spreadsheet or a dedicated resource management tool. Cost rates are stored in a custom field on the Card if the Trello Workspace has the Custom Fields Power-Up enabled.

Planisware stores project-to-project and task-to-task dependencies in a separate link table. Trello has no structured dependency graph. We extract the full dependency graph and create cross-board card links using Trello's 'Link Cards' feature to represent the most critical dependencies (finish-to-start and start-to-start). Dependencies that cannot be represented as card links are documented in a Dependency Map delivered as a CSV and JSON file for the customer to manage outside Trello or recreate using a Trello Power-Up designed for dependency tracking.

Planisware financial objects include budgets, actuals, forecasts, and cost codes with custom field extensions. Trello has no native financial object or budget tracking. We extract budget amounts, cost code values, and financial period allocations as numeric custom fields on the Board-level or Card-level using Trello's Custom Fields Power-Up (available on the Free plan via the Amazing Fields Power-Up or on Standard and above natively). Financial period rollups and cost code hierarchies are documented as a separate Financial Gap Report since Trello cannot perform multi-card financial aggregation natively.

Planisware cost codes are stored as structured financial objects with hierarchical coding schemes. Trello Labels can serve as a lightweight cost code proxy if the number of codes is small (under 50). For larger or more complex cost code structures, we store the cost code as a text custom field on each Card and document the code hierarchy in a lookup table delivered alongside the migration. Customers who need hierarchical cost code rollups use a reporting Power-Up or a connected Google Sheets/Excel model post-migration.

Planisware's custom fields on any object are frequently used and highly implementation-specific. Trello supports custom fields at the Card level (text, number, date, dropdown, checkbox, rating) on Standard and Premium plans, or via the Amazing Fields Power-Up on Free. We catalog every Planisware custom field during scoping, map each to an equivalent Trello custom field type or Label, and create the destination custom field schema before migration. Custom fields with complex picklist values are migrated as dropdown or text custom fields depending on the available Trello field types in the customer's plan.

Task-level custom fields in Planisware (often tracking regulatory compliance flags, approval status, or custom metrics) map to Trello Card custom fields using the same type-mapping logic as project-level fields. Date fields map to Trello date custom fields; numeric fields map to number fields; text fields map to text or dropdown fields. Checkbox fields map directly to Trello checkbox custom fields. Any custom field with a dependency on a Planisware financial object or resource allocation is flagged as a gap and documented separately.

Planisware User accounts and owner assignments are extractable. We extract every distinct user referenced as a project owner or activity assignee and match by email against the Trello Workspace members. The customer must provision the Trello Workspace and invite members before migration. We resolve owner assignments by email match; any Planisware user without a matching Trello member is held in a reconciliation queue. Role and permission mapping from Planisware's role hierarchy to Trello's Board role (Admin, Member, Observer) is documented in a permissions gap analysis since Trello's permission model is simpler and does not support fine-grained object-level permissions.

Planisware status workflows and pipeline stages are configured per implementation. Trello Lists serve as the stage proxy for task workflow. We map Planisware status values to Trello List names using a customer-approved status mapping table created during scoping. If Planisware has more than 10 distinct status values, we consolidate them into a maximum of 10 Lists (Trello's practical limit for usability) and document the mapping. Custom status workflow logic (automated transitions, approval gates) cannot migrate; we document each workflow as a written specification for the customer to rebuild in Trello Butler.

Planisware documents are stored in a proprietary format that requires the Planisware application to retrieve. We do not migrate document blobs. We extract document metadata (filename, linked object, upload date, document description) and create Trello Card attachments pointing to the original file store location if the customer has extracted their file store separately. If the original file store is unavailable, we document the document metadata in a gap report for manual re-upload post-migration. Customers using Planisware's MS Office 365 integration should extract documents from the linked SharePoint or OneDrive location before migration.

Planisware Enterprise supports backlog management, sprint planning, and PI coordination for teams using Agile at scale. Trello boards support Agile-style workflow but do not have native sprint objects. We extract sprint names, sprint goals, and sprint membership and map them to Trello Labels (one per sprint) with the sprint goal stored as a Card description on a sprint-anchor Card. Teams requiring native sprint tracking in Trello use the Premium plan's native Timeline and Calendar views or a dedicated Agile Power-Up.

Planisware Enterprise frequently integrates with ERP systems for cost actuals, budget actuals, and financial forecasting. Trello has no native ERP integration. We extract the most recent ERP-synced financial values (actuals, commitments, forecasts) as custom fields on Planisware project records and store them as Trello Card custom fields. The ERP integration itself is documented as a gap: the customer must establish a new data feed from their ERP to a connected tool (Google Sheets, Smartsheet, or a dedicated integration) or rebuild the financial view in Trello using a reporting Power-Up.