Migrate from Planisware Enterprise to monday Work Management

Planisware Projects map to monday.com Boards. The project name becomes the Board name, project dates map to the Board's date range columns, project status maps to a Status column with Planisware stage values remapped to monday.com-compatible status labels. Custom fields on the Planisware project object become custom columns on the monday.com Board. The Planisware project identifier is preserved in a text column for audit traceability.

Planisware Portfolios map to monday.com Boards. Member projects are linked via an Integrations column (connecting to sub-Board links) or flattened into Groups within a single portfolio Board. Portfolio-level budget data migrates as number or currency columns. monday.com's basic portfolio roll-up is used for cross-board reporting; organizations needing advanced portfolio simulation must rebuild those models in monday.com or a dedicated BI tool.

Planisware Resource records map to monday.com Team Members. Allocation percentages per project map to Workload view settings or to a number column per Board. Skill profiles and cost rates migrate as text and number columns respectively. monday.com's Workload view provides allocation visualization but lacks Planisware's AI-powered capacity optimization; the customer's admin must configure workload rules manually post-migration.

Planisware multi-level WBS structures are flattened into monday.com's Item-plus-single-subitem model. The top two levels of the Planisware WBS become Items at the Board level; the third level and deeper become Subitems. We preserve the original WBS path (e.g., 1.2.3) in a text column on each Item so the original hierarchy is auditable even after flattening. Milestone tasks in Planisware become a separate Status value or a date-only column in monday.com.

Planisware supports finish-to-start, start-to-start, finish-to-finish, and lead/lag dependency types. monday.com supports only finish-to-start dependencies via its dependency column. We extract the full Planisware dependency graph, map all dependency types to finish-to-start (dropping lead/lag offsets into a days_offset column), and rehydrate the surviving links in monday.com's dependency column during import. Teams requiring non-FS dependency types must rebuild using monday.com's automation framework.

Planisware budget, actuals, forecast, and cost code financial data migrate as number or currency columns on the corresponding Board Items. We map Planisware cost codes to a text column and financial values to the appropriate number column. Cost breakdown structures with multi-level coding (e.g., WBS-cost code) are flattened into a single cost_description column. monday.com has no native cost ledger; organizations needing financial simulation or variance analysis must use a connected BI tool or rebuild the model in monday.com's formula columns.

Planisware custom fields are highly implementation-specific and are enumerated during the pre-migration schema discovery phase. Each custom field is mapped to a monday.com custom column of the closest matching type (text, number, date, person, status, dropdown, multi-select). monday.com does not have a centralized custom field configuration; we apply column settings per Board using template-based configuration during import.

Planisware custom status workflows and pipeline stage values are mapped to monday.com Status columns using a customer-approved status mapping table created during scoping. The mapping preserves stage ordering and any conditional color coding. New status values added after migration must be manually added to the monday.com Status column by the admin.

Planisware User records map to monday.com Team Members. Owner assignments on Projects and Activities are resolved by email match to the monday.com workspace. Any Planisware Owner without a matching monday.com User is held in a reconciliation queue for the customer's admin to provision before the Owner mapping phase completes. Role and permission structures do not migrate because monday.com's permission model differs fundamentally from Planisware's role-based access.

Planisware documents are stored in a proprietary format that cannot be accessed without the Planisware application. We do not migrate document blobs. We extract document metadata (filename, linked object reference, upload date, upload user) into a document_inventory CSV. The customer extracts the original file store separately and re-uploads documents to monday.com Items post-migration using a provided re-attach script that maps Planisware object references to monday.com Item IDs.

Planisware tracks project engagements and activity logs that can be mapped to monday.com's Item Activity log (updates column). We preserve the most recent engagement entries as manual text notes on Items since monday.com does not have a native engagement object model. High-volume engagement history is summarized rather than fully reconstructed.

Planisware cross-project linkages and program structures map to monday.com's Integration column (linked boards) where a sub-Board represents a subsidiary project. We build a program Board that aggregates member project Boards via the Integration column. Organizations with complex program hierarchies may need to restructure post-migration as monday.com does not natively support multi-level program-portfolio hierarchies.