How long does a workspace.pm to Microsoft Project migration take?

Most migrations land between four and eight weeks for accounts with fewer than 100 projects and 5,000 tasks. Migrations with complex multi-level task hierarchies, large resource allocation histories, or portfolio-level groupings requiring manual tag reconstruction move to eight to fourteen weeks because of export coordination time with workspace.pm and the hierarchy flattening work required to represent nested subtasks in Microsoft Project's WBS model.

Does workspace.pm have an API we can use for migration?

No. Research found no public API documentation, authentication scheme, or export endpoint for workspace.pm. Migration depends on vendor-assisted data exports or admin console downloads. We coordinate the export request on your behalf and validate the resulting file format before building the ingestion pipeline. This export coordination step is the primary timeline variable for this migration pair and can add two to four weeks compared to migrations from platforms with documented REST APIs.

What happens to workspace.pm Kanban boards, Gantt charts, and dashboards after migration?

These are presentation-layer objects that are not stored as discrete data records and therefore do not migrate. The underlying task dates, dependencies, and milestones that power the Gantt chart do migrate and will render in Microsoft Project's Gantt view automatically. Kanban board layouts and dashboard reports require manual reconstruction in Microsoft Project or Power BI. We deliver a written report listing every workspace.pm dashboard and Kanban board configuration as documented during the audit, with notes on how to rebuild each view from the migrated data.

What does a workspace.pm to Microsoft Project migration cost?

Migrations under 100 projects and 5,000 tasks typically land between $5,000 and $8,000 and complete in four to six weeks. Migrations with large task hierarchies, complex resource allocation records, portfolio groupings, or time entry histories move to $10,000-$16,000 and eight to fourteen weeks because of the additional export coordination and WBS hierarchy work. Microsoft Project Plan 1 ($10/user/month), Plan 3 ($30/user/month), and Plan 5 ($55/user/month) licensing costs sit outside the migration fee and remain the customer's recurring subscription cost.

Can we migrate workspace.pm custom fields to Microsoft Project?

Yes, with pre-migration capture. We map workspace.pm custom fields by data type to Microsoft Project's built-in custom field types: Text fields map to Text1-30, dates to Date1-10, flags to Flag1-10, numbers to Number1-20, and cost values to Cost1-10. Picklist values in workspace.pm map to Microsoft Project lookup tables for the corresponding custom field. The constraint is that the custom field schema must be documented from workspace.pm before decommissioning because schema definitions are often not included in data exports. We request a schema capture during the pre-migration audit.

How do we handle workspace.pm portfolios in Microsoft Project?

Microsoft Project has no native multi-project portfolio container. We handle this in one of two ways depending on your choice during scoping. First, we can add a custom Text field to each migrated project record in Microsoft Project called PortfolioName (or equivalent) and populate it from the workspace.pm portfolio membership list we extract during the pre-migration audit. This allows cross-project filtering and Power BI portfolio views. Second, for Project Online destinations, we can configure a SharePoint list on the project site that stores the portfolio-to-project membership for querying in Power BI. The customer chooses the approach before production migration.

Do workspace.pm workflows and automations migrate to Microsoft Project?

No. Workspace.pm workflows and automations do not migrate as code because they represent business process logic specific to the source platform. We deliver a written inventory of every active workspace.pm workflow and automation with its trigger, conditions, actions, and a recommended Microsoft Project or Power Automate equivalent. The customer's admin rebuilds these in Microsoft Project task scheduling logic or Power Automate flows post-migration. Power Automate workflows do not carry a separate licensing cost for organizations already on Microsoft 365 E3 or E5, but the rebuild effort is outside the migration scope.

What about Microsoft Project Online retirement? Does that affect our migration to Microsoft Project?

Microsoft Project Online is retiring on September 30, 2026, with new instance creation blocked as of April 2026. If your destination is Microsoft Project Plan 3 or Plan 5 (desktop or the web version), this retirement does not directly affect you. If you are considering Project Online as the destination, we recommend migrating to Project Plan 5 (the successor cloud experience) or Project Server SE instead. We can advise on the destination edition as part of the discovery phase. The Project Online retirement does not affect the workspace.pm source side of this migration; it affects only the destination platform choice.

workspace.pm to Microsoft Project Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from workspace.pm to Microsoft Project requires navigating a platform that has no accessible API on the source side and a different architectural model on the destination. workspace.pm organizes work around a portfolio hierarchy with Projects, Tasks, Subtasks, and a Resource management layer; Microsoft Project uses a flat schedule-based model with tasks, dependencies, and resources but no native multi-project portfolio aggregation. The absence of a documented workspace.pm API means we coordinate with your vendor contact or admin console to extract the data before we can build the migration pipeline. We reconstruct portfolio-to-project associations as tag or custom field groupings in Microsoft Project, since there is no equivalent portfolio container. Custom field schemas must be captured from workspace.pm before decommissioning because the schema definition itself is often not included in exports. We do not migrate Gantt chart view configurations, Kanban board layouts, or dashboard reports as these are presentation-layer objects derived from underlying task data; we deliver the raw data so your team can rebuild these views in Microsoft Project. Workflows and automations do not migrate and are inventoried for your admin to rebuild in Microsoft Project or Power Automate post-migration.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

workspace.pm

What's pushing teams away

The platform is positioned for enterprise PMOs rather than small teams, so smaller organizations find the feature set and pricing model excessive for their needs.
Like many enterprise PM tools, the UI and workflow configuration can be complex for team members who only need to log time or check task status, driving adoption resistance.
Organizations seeking lighter-weight, consumer-grade PM tools may switch to platforms with lower learning curves and simpler onboarding.
Teams that rely heavily on native integrations with adjacent tools (HR systems, CRMs) report friction when workspace.pm lacks pre-built connectors.

Choosing

Microsoft Project

What's pulling them in

Organizations already running Microsoft 365 and Azure AD adopt Microsoft PPM because it slots into existing identity, Teams, and SharePoint infrastructure without requiring a separate identity provider or SSO vendor.
Enterprise PMOs choose it for critical-path scheduling, baseline comparison, cross-project dependencies, and resource utilization reporting that standalone PM tools cannot replicate at this depth.
Project Online's integration with Power BI gives portfolio-level dashboards and cost-rollup reporting that satisfies executive governance requirements without third-party BI tooling.
Government, financial services, and healthcare organizations select it because FedRAMP, ISO 27001, and SOC 2 compliance certifications meet enterprise procurement requirements out of the box.
Large IT departments default to it as the market-leader in project portfolio management software, often driven by corporate licensing agreements that bundle it with other Microsoft 365 seats.

Object mapping

How workspace.pm objects map to Microsoft Project

Each row shows how a workspace.pm object lands in Microsoft Project, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

workspace.pm

Project

maps to

Microsoft Project

Project

1:1

Fully supported

workspace.pm Projects map 1:1 to Microsoft Project files (MPP) or Project Online projects. We migrate Project Name, Project Status, Start Date, Finish Date, Project Owner, and any project-level cost fields. Archived or completed projects migrate with their historical data intact. The destination project is created first as the parent container before any tasks, resources, or assignments are imported.

workspace.pm

Task

maps to

Microsoft Project

Task

1:1

Fully supported

workspace.pm Tasks map to Microsoft Project Task records with Name, Start, Finish, Duration, Priority, and Status preserved. The task summary level (whether a task is a parent or leaf node) maps to the Outline Level and Summary field in Microsoft Project. Task hierarchy from workspace.pm is preserved as WBS hierarchy in the destination.

workspace.pm

Subtask

maps to

Microsoft Project

Task (child)

1:many

Fully supported

workspace.pm Subtasks nest under parent Tasks. We flatten this to Microsoft Project's Task with Subtasks model, where the child subtask becomes a subordinate Task record with the same parent project and a Summary task above it. The ordering sequence from workspace.pm maps to the ID and Outline Number in Microsoft Project so the hierarchy reads correctly in Gantt views.

workspace.pm

Milestone

maps to

Microsoft Project

Task (Milestone)

1:1

Fully supported

workspace.pm Milestones with name, target date, and associated project linkage map to Microsoft Project Task records with the Milestone flag set to Yes and the Finish date set to the milestone date. Where workspace.pm milestones have no duration they are imported with zero days so they render correctly on the Gantt timeline.

workspace.pm

Dependency

maps to

Microsoft Project

Task Dependency

lossy

Fully supported

workspace.pm predecessor-successor relationships map to Microsoft Project task dependencies using Finish-to-Start, Start-to-Start, Finish-to-Finish, and Start-to-Finish link types as specified in the source data. We reconstruct the dependency pairs using the unique task IDs resolved during the task import phase and assign the correct predecessor task reference to each dependent task.

workspace.pm

Custom Field

maps to

Microsoft Project

Custom Field (Text, Date, Flag, Number, Cost)

lossy

Fully supported

workspace.pm custom fields at the project and task level are extracted by data type and mapped to the closest Microsoft Project custom field type. Text values map to Text1-30, dates to Date1-10, flags to Flag1-10, numbers to Number1-20, and cost values to Cost1-10. We request the full custom field schema from workspace.pm during the pre-migration audit, including picklist options for choice-based fields, before building the field mapping document.

workspace.pm

Assignee / Resource

maps to

Microsoft Project

Resource

lossy

Fully supported

workspace.pm Resource management records (user name, role, allocation percentage, and date range) map to Microsoft Project Resource Sheet entries. Each resource is created with a name, type (Work or Material), Max Units, and a calendar. We extract the resource allocation percentages and map them to assignment-level Units on the TaskUsage or ResourceUsage view.

workspace.pm

Resource Assignment

maps to

Microsoft Project

Task Assignment

1:1

Fully supported

workspace.pm assignments linking a resource to a task with percentage allocation map to Microsoft Project Assignments with OwnerId resolved to the resource name, Units set to the allocation percentage (as a decimal), and Work calculated from the task duration and assignment units. Assignment actuals (hours logged) migrate as assignment-level actual work entries.

workspace.pm

Time Entry

maps to

Microsoft Project

Assignment Actual Work

1:1

Fully supported

workspace.pm time tracking entries (user, date, hours, description) map to Microsoft Project assignment-level actual work entries. We map the date and hours to the Assignment Timesphane Data or directly to the Actual Work field per assignment. Where the destination is Project Online, time entries can be logged through Project Web App timesheets post-migration using the migrated hours as the opening balance.

workspace.pm

Comment

maps to

Microsoft Project

Task Note

1:1

Fully supported

workspace.pm discussion threads on tasks migrate to Microsoft Project Task Notes. We extract the comment text, author name, and timestamp. In Project Online, comments can alternatively be stored as a SharePoint list attached to the project site for threaded discussion. The customer chooses between task notes or a linked SharePoint list during scoping.

workspace.pm

Attachment

maps to

Microsoft Project

Document (SharePoint or Project)

1:1

Fully supported

File attachments linked to tasks or projects export as URLs or file references depending on what workspace.pm's admin export exposes. We transfer attachment metadata (filename, uploader, upload date, file URL) and note the reference in the migration inventory. For Project Online destinations, attachments are linked to the project SharePoint document library; for desktop MPP files, attachment references are noted in the handoff document for manual relinking.

workspace.pm

Portfolio

maps to

Microsoft Project

Tag or Custom Field Grouping

many:1

Fully supported

workspace.pm portfolios aggregate multiple projects under a single executive view. Microsoft Project has no native portfolio container. We export the portfolio-to-project membership list from workspace.pm during the pre-migration audit and reconstruct the grouping as a custom Text field on each project record (e.g., PortfolioName) or as tags in Project Online. This allows the customer to filter cross-project views and Power BI portfolio reports without a native portfolio object.

workspace.pm	Microsoft Project	Compatibility
Project	Project1:1	Fully supported
Task	Task1:1	Fully supported
Subtask	Task (child)1:many	Fully supported
Milestone	Task (Milestone)1:1	Fully supported
Dependency	Task Dependencylossy	Fully supported
Custom Field	Custom Field (Text, Date, Flag, Number, Cost)lossy	Fully supported
Assignee / Resource	Resourcelossy	Fully supported
Resource Assignment	Task Assignment1:1	Fully supported
Time Entry	Assignment Actual Work1:1	Fully supported
Comment	Task Note1:1	Fully supported
Attachment	Document (SharePoint or Project)1:1	Fully supported
Portfolio	Tag or Custom Field Groupingmany:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

workspace.pm gotchas

High

No public API documentation found for workspace.pm

Medium

Presentation-layer objects are not migratable

Medium

Portfolio data may not exist as a standalone exportable object

Low

Custom field schemas must be captured before decommissioning the source

Microsoft Project gotchas

High

Project for the web is being retired and merged into Microsoft Planner

Medium

Planner-tier portfolio features are incomplete despite Plan 5 labeling

Medium

Web app constraint controls are weaker than the Windows desktop client

High

Project requires a separate license not bundled with standard Microsoft 365

Medium

Project Online API is edition-gated and inconsistently documented

workspace.pm gotchas		Microsoft Project gotchas
Severity	Issue	Severity	Issue
High	No public API documentation found for workspace.pm	High	Project for the web is being retired and merged into Microsoft Planner
Medium	Presentation-layer objects are not migratable	Medium	Planner-tier portfolio features are incomplete despite Plan 5 labeling
Medium	Portfolio data may not exist as a standalone exportable object	Medium	Web app constraint controls are weaker than the Windows desktop client
Low	Custom field schemas must be captured before decommissioning the source	High	Project requires a separate license not bundled with standard Microsoft 365
		Medium	Project Online API is edition-gated and inconsistently documented

Pair-specific challenges

workspace.pm has no documented public API

Research across multiple query types found no API endpoint documentation, authentication scheme, or export API for workspace.pm. Migration is dependent on vendor-assisted exports or manual CSV and JSON downloads from the admin console. We flag this upfront during scoping and request a data export package from workspace.pm support or the customer admin before we can build the migration pipeline. Without a supported export mechanism, migration timelines extend significantly because the data must be extracted manually or through a vendor engagement. We coordinate directly with workspace.pm on your behalf to request the export and validate the file format before pipeline build begins.
Portfolio-to-project associations may not export as discrete records

workspace.pm's portfolio layer aggregates multiple projects for executive reporting. Our research did not confirm whether portfolio-to-project associations export as a discrete data set or must be reconstructed from project metadata. We include a pre-migration data audit step that extracts the portfolio membership list from workspace.pm's admin panel or reporting export before building the migration map. Where portfolios do not export cleanly, we create tag-based groupings in Microsoft Project using a custom Text field so that cross-project filtering and portfolio-style views remain available post-migration.
Custom field schemas must be captured before source decommissioning

workspace.pm supports custom fields at the project and task level, but the schema definition (field names, data types, and picklist options) is often not included in data exports. We request a full schema export or screen capture of the custom field admin panel as part of the pre-migration audit. Without the schema, we cannot pre-create the corresponding custom fields in Microsoft Project and must map everything as Text fields, losing type fidelity. Picklist option values between workspace.pm and Microsoft Project lookup tables are handled explicitly during the mapping phase and documented in the field mapping reference.
Kanban boards, Gantt charts, and reports are not migratable

workspace.pm's Kanban boards, Gantt chart views, and dashboard reports are UI rendering constructs derived from underlying task and project data. These view configurations are not stored as independent exportable objects and therefore do not migrate. During scoping we confirm with the customer which reports represent critical business records versus UI preferences. Critical reports may require manual reconstruction in Microsoft Project using the migrated underlying data as the source, or export of the data to Power BI for rebuilt portfolio dashboards. The Gantt chart rendering in Microsoft Project will automatically reconstruct from the migrated task dates, dependencies, and milestones.

Migration approach

Six steps for a successful workspace.pm to Microsoft Project data migration

Export coordination and pre-migration audit

Because workspace.pm has no documented API, we open a coordinated export request with your workspace.pm vendor contact or admin team. We provide them with a structured data request covering Projects, Tasks, Subtasks, Milestones, Dependencies, Resource assignments, Time entries, Custom field schema, and portfolio membership. During this window we also document the workspace.pm custom field admin panel (field names, types, picklist options) via screen capture or schema export. This step determines whether the export comes as CSV, JSON, or a vendor-assisted format, which shapes the ingestion pipeline we build.
Data validation and portfolio reconstruction planning

We validate the export package against the documented object counts (project count, task count, resource count, attachment count) to confirm the export is complete. We identify any portfolio-to-project associations and determine whether they export as discrete records or must be reconstructed from project metadata. We document any custom field schema gaps where the export did not include field definitions and request additional schema documentation from the source admin. The output of this step is a signed data validation report and a written mapping plan for the customer to approve before pipeline build.
Destination schema preparation

We configure the Microsoft Project destination environment. For Project Online destinations, this includes provisioning the project site, configuring the Enterprise Custom Fields (using the workspace.pm schema as mapped to Microsoft Project custom field types), and setting up the Resource Sheet with the imported resources and their availability calendars. For desktop MPP destinations, we prepare the template project file with the required custom fields pre-configured. We do not build automations or workflows in this step; we configure only the data structure that will receive the migrating records.
Sandbox or pilot migration

We run a full migration into a sandbox environment for Project Online or a copy of the destination file for desktop, using a representative subset of projects (at least one simple project, one with complex dependencies, and one with resource allocation). We reconcile record counts for every object type, spot-check task hierarchies and dependency links on 25-50 randomly sampled records, and validate that custom field values transferred with correct data types. The customer signs off on the pilot results before we proceed to production migration. Any mapping corrections identified in the pilot are applied before the production run.
Production migration in dependency order

We run production migration in record-dependency order: Resources (first, so they are available for assignments), Projects, Tasks with hierarchy preserved, Milestones, Dependencies (after task IDs are resolved), Assignments with resource links, Time entries as assignment actuals, Custom field values, Comments as task notes, and Attachment metadata. Each phase emits a row-count reconciliation report. Portfolio groupings are applied as a custom Text field on each project record during or after the project import phase.
Cutover, validation, and workflow handoff

We freeze workspace.pm writes during the cutover window, run a final delta migration for any records modified during migration, and hand over a written inventory of workflows, automations, and reports that require manual rebuild in Microsoft Project or Power Automate. We do not rebuild these as part of the migration scope. We support a one-week post-cutover window to resolve any data quality issues reported by the customer's project team. The customer receives the migration map document, the data validation report, and the automation inventory as permanent records of the migration.

Platform deep dives

Context on both ends of the pair

workspace.pm

Source

Strengths

Portfolio-level project aggregation with real-time dashboards for executive visibility across 10,000+ projects.
Dual deployment — managed cloud with 99.9% uptime or on-premises for data residency compliance.
ISO 27001-certified data center with structured security controls for enterprise procurement.
Integrated resource planning with capacity visualization and allocation percentage tracking.
Structured task hierarchy supporting Projects, Tasks, Subtasks, Milestones, and Dependencies.

Weaknesses

No publicly documented API surfaced in research, limiting programmatic export and making data extraction dependent on manual or vendor-assisted exports.
Kanban boards, Gantt charts, and dashboard reports are presentation-layer views — their configurations are not exportable as discrete data objects.
Pricing is enterprise-negotiated (contact sales), with no published per-user or tier breakdown, making cost comparison difficult pre-purchase.
The platform targets large PMOs; smaller teams may find the interface heavy and the feature set over-engineered for simple task management.

Microsoft Project

Destination

Strengths

Deep critical-path scheduling with baseline comparison and cross-project dependency tracking unmatched by lighter PM tools.
Native Azure AD authentication, Teams integration, and Power BI reporting sit on infrastructure enterprises already license and manage.
Enterprise governance controls including demand intake workflows, resource request approval, and portfolio-level capacity analysis.
Supports both Waterfall and Agile methodologies within the same project, accommodating hybrid delivery teams.
Scalable from Project Plan 1 for small teams to Project Server on-premises for regulated industries with strict data-sovereignty requirements.

Weaknesses

Ease-of-use scores trail the category average by a wide margin; onboarding friction frustrates new users consistently across G2 and Capterra reviews.
Pricing ranks 42nd of 49 tools in its category — the total cost of ownership including IT administration and training is rarely recovered for small or mid-market teams.
No built-in client portal, external stakeholder sharing, or proofing workflow, limiting use cases to internal PMO environments only.
The web interface (Project for the web / Planner Premium) has materially weaker constraint controls and resource auto-leveling than the Windows desktop client.
Project for the web is being consolidated into Microsoft Planner, creating uncertainty about which product tier will host project portfolio data long-term.

	workspace.pm Source	Microsoft Project Destination
Strengths	Portfolio-level project aggregation with real-time dashboards for executive visibility across 10,000+ projects. Dual deployment — managed cloud with 99.9% uptime or on-premises for data residency compliance. ISO 27001-certified data center with structured security controls for enterprise procurement. Integrated resource planning with capacity visualization and allocation percentage tracking. Structured task hierarchy supporting Projects, Tasks, Subtasks, Milestones, and Dependencies.	Deep critical-path scheduling with baseline comparison and cross-project dependency tracking unmatched by lighter PM tools. Native Azure AD authentication, Teams integration, and Power BI reporting sit on infrastructure enterprises already license and manage. Enterprise governance controls including demand intake workflows, resource request approval, and portfolio-level capacity analysis. Supports both Waterfall and Agile methodologies within the same project, accommodating hybrid delivery teams. Scalable from Project Plan 1 for small teams to Project Server on-premises for regulated industries with strict data-sovereignty requirements.
Weaknesses	No publicly documented API surfaced in research, limiting programmatic export and making data extraction dependent on manual or vendor-assisted exports. Kanban boards, Gantt charts, and dashboard reports are presentation-layer views — their configurations are not exportable as discrete data objects. Pricing is enterprise-negotiated (contact sales), with no published per-user or tier breakdown, making cost comparison difficult pre-purchase. The platform targets large PMOs; smaller teams may find the interface heavy and the feature set over-engineered for simple task management.	Ease-of-use scores trail the category average by a wide margin; onboarding friction frustrates new users consistently across G2 and Capterra reviews. Pricing ranks 42nd of 49 tools in its category — the total cost of ownership including IT administration and training is rarely recovered for small or mid-market teams. No built-in client portal, external stakeholder sharing, or proofing workflow, limiting use cases to internal PMO environments only. The web interface (Project for the web / Planner Premium) has materially weaker constraint controls and resource auto-leveling than the Windows desktop client. Project for the web is being consolidated into Microsoft Planner, creating uncertainty about which product tier will host project portfolio data long-term.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from workspace.pm to Microsoft Project

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

workspace.pm

Microsoft Project

How workspace.pm objects map to Microsoft Project

What specifically takes care here

Six steps for a successful workspace.pm to Microsoft Project data migration

Context on both ends of the pair

How hard is this migration?

Estimate your workspace.pm to Microsoft Project migration cost

What are you migrating?

Frequently asked questions about workspace.pm to Microsoft Project data migrations

Can't find your answer?

Related migrations to explore

Move from workspace.pm.
Land in Microsoft Project, intact.

Migrate from workspace.pm to Microsoft Project

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

workspace.pm

Microsoft Project

How workspace.pm objects map to Microsoft Project

What specifically takes care here

Six steps for a successful workspace.pm to Microsoft Project data migration

Context on both ends of the pair

How hard is this migration?

Estimate your workspace.pm to Microsoft Project migration cost

Frequently asked questions about workspace.pm to Microsoft Project data migrations

Can't find your answer?

How long does a workspace.pm to Microsoft Project migration take?

Does workspace.pm have an API we can use for migration?

What happens to workspace.pm Kanban boards, Gantt charts, and dashboards after migration?

What does a workspace.pm to Microsoft Project migration cost?

Can we migrate workspace.pm custom fields to Microsoft Project?

How do we handle workspace.pm portfolios in Microsoft Project?

Do workspace.pm workflows and automations migrate to Microsoft Project?

What about Microsoft Project Online retirement? Does that affect our migration to Microsoft Project?

Related migrations to explore

Move from workspace.pm. Land in Microsoft Project, intact.

Move from workspace.pm.
Land in Microsoft Project, intact.