Migrate your Deltek Project Portfolio Management data

Projects are the top-level container. We extract full project headers, status, billing type, and project manager assignment from both the Project List Export report and the planning data CSV. The WBS hierarchy below each project migrates as a nested structure in the destination PM tool.

WBS elements are exported as part of the Project List Export and Planning Data Export. We preserve the numeric and text identifiers from Deltek so WBS-level rollups compute correctly in the destination.

Deltek Resources (employees, consultants, equipment) export via the Planning Data Export CSV with utilization and rate data. We map Deltek Resource IDs to the destination's resource directory and flag cases where a consultant row must be created as a vendor or a vendor must be created as a resource in the target system.

Task-to-resource assignments are available in the planning CSV. Assignment hours and dates migrate, but Deltek-specific scheduling engine nuances (such as effort-driven vs. duration-driven scheduling) are not always representable 1:1 in other platforms and require explicit flagging.

Deltek baselines are stored as distinct plan snapshots. We export the current published baseline for both schedule and budget curves and import them as baseline variants in the destination. Unpublished plan versions are not exported unless the customer explicitly requests them.

Planning Data Export provides planned labor hours, expense amounts, and consultant costs in separate columns. We chunk these by cost type and map them to the destination's budget line-item schema. Custom cost codes in Deltek require field-level mapping work during scoping.

Custom fields defined via the User-Defined Data form export with the Project List Export. We handle text, number, date, and picklist types. Picklist values must be mapped to the destination's picklist or converted to free text if no matching taxonomy exists.

Deltek PIM exports documents in a folder structure mirroring the PIM pool. We extract the archive, reconstruct the project-relative folder tree, and attach files to their parent Project in the destination. Documents without a clear parent project are surfaced for manual review.

Deltek Risk registers export as structured data. Most destination PM tools do not have a native Risk object, so we import risks as Issues or Tasks with a risk flag and preserve the risk score, probability, and mitigation notes as custom fields.

Milestones are exported via the Project List Export. We preserve milestone dates, names, and deliverables. Flagged milestones and constraint types migrate as properties.

Deltek PPM is not a CRM; it does not manage lifecycle stages like Lead or Opportunity. We do not migrate pipeline data from Deltek PPM because no such object exists in this product's schema.

Time entry capture is handled by Deltek Ajera or Deltek Costpoint in the Deltek ecosystem, not by the standalone PPM tools. Time entries do not live in the PPM data model and are not available for export via the planning data CSV.