How long does a OneDeck to Microsoft Project migration take?

Migrations land between three and five weeks for single-board structures under 5,000 tasks with straightforward task hierarchies. Migrations with multiple boards requiring consolidation, subtask hierarchies exceeding three levels, explicit dependency mapping across 50 or more tasks, or resource pool configuration move to six to ten weeks. The dependency analysis step is the most time-intensive phase and directly correlates to project complexity.

What does a OneDeck to Microsoft Project migration typically cost?

Migrations under 5,000 tasks and a single board structure range from $4,500 to $7,000. Migrations with multiple boards, complex subtask hierarchies, explicit dependency mapping, resource pool configuration, or large attachment volumes range from $9,500 to $14,000. Microsoft Project subscription costs (Project Plan 1 at $10/user/month, Project Plan 3 at $30/user/month, Project Plan 5 at $55/user/month) sit outside the migration fee as the customer's recurring licensing cost.

Can we migrate to Microsoft Planner instead of MS Project?

Yes. Microsoft announced the retirement of Project for the web in August 2025, redirecting users to Microsoft Planner. If the customer prefers a kanban-style interface similar to OneDeck rather than a Gantt-centric desktop tool, Microsoft Planner may be a better fit. Planner uses buckets and checklists rather than WBS-coded tasks and has a shallower learning curve. We support migration to both MS Project and Microsoft Planner; the destination choice depends on the customer's PM methodology requirements and team familiarity with formal scheduling tools.

Do task comments and attachment history migrate?

Task comments migrate as timestamped text appended to the MS Project task Notes field, subject to OneDeck API accessibility (not all plans expose comment history). Document attachments migrate as file links on the relevant MS Project task. However, OneDeck Document Builder PDFs do not preserve their rendered formatting; the data content transfers but the branded layout does not survive export. We recommend a post-migration document review to verify formatting integrity for customer-facing documents.

How do we handle task dependencies that OneDeck does not model?

OneDeck kanban boards do not have explicit predecessor-successor relationship modeling. We analyze the task sequence during the dependency analysis step, infer likely dependencies from column progression and task ordering, and present a dependency mapping proposal for the customer's PM to approve. Migrations without explicit dependency input result in MS Project schedules where tasks have no calculated float, which limits the value of critical path analysis. We strongly recommend investing time in the dependency proposal review before production migration.

What happens to OneDeck custom fields in MS Project?

OneDeck custom fields on tasks map to MS Project Enterprise Custom Fields. We extract field definitions during discovery, map field types (text to Text, number to Number, date to Date), and assign them to the relevant custom field slots. Note that MS Project custom fields behave differently across views: task-level custom fields do not appear in Resource view and vice versa. We document custom field availability per view during the mapping phase and advise the customer to validate in their actual working views post-migration.

Is Microsoft Project Online safe to migrate to given the retirement announcement?

Project for the web (the browser-based roadmap tool) retires in August 2025, but MS Project Online (the cloud-based project management platform with the full feature set) is not retiring. Organizations migrating to Project Online should confirm they are targeting the full project management product, not the roadmap companion app. We clarify the destination product family during scoping. If the customer wants a cloud-native Microsoft PM tool but needs a more collaborative interface, Microsoft Planner is the replacement for Project for the web and may be a better fit than the Gantt-centric MS Project Online.

OneDeck to Microsoft Project Migration — Field-Level Mapping & Rollback

Why teams make this switch

Two sides of the same decision

Leaving

OneDeck

What's pushing teams away

Small teams may outgrow the bundled all-in-one model when they need the depth of specialized tools like dedicated CRM or advanced resource management platforms
Advanced project management features for large-scale enterprise portfolios are limited compared to purpose-built enterprise project management suites
Multi-board reporting across different workspaces can require manual consolidation, reducing visibility for operations teams managing multiple business units
Customization depth for industry-specific workflows may require workarounds or developer assistance that smaller teams lack access to

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 OneDeck objects map to Microsoft Project

Each row shows how a OneDeck 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.

OneDeck

Board

maps to

Microsoft Project

Project

1:1

Fully supported

OneDeck Boards map 1:1 to MS Project Projects. Board name becomes Project Name; board description becomes Project Summary. The board's default view orientation (kanban vs table) does not map directly to MS Project since MS Project defaults to Gantt, but we preserve the board's column structure as a reference for rebuilding views post-migration. Multiple OneDeck boards may consolidate into a single MS Project Program if the customer requires cross-board portfolio tracking.

OneDeck

Task

maps to

Microsoft Project

Task

1:1

Fully supported

OneDeck Tasks map directly to MS Project Tasks. Task Name, Description (as Notes), Start Date, Due Date, and Status migrate to TaskName, Notes, Start, Finish, and PercentComplete respectively. OneDeck subtasks map to MS Project subtasks under the parent task hierarchy. WBS numbering is auto-generated during import based on the task hierarchy depth.

OneDeck

Task Status

maps to

Microsoft Project

Task PercentComplete or Status Field

lossy

Fully supported

OneDeck status column values (To Do, In Progress, Done) map to MS Project task status and PercentComplete. We configure a status mapping table during scoping: Done maps to 100% complete, In Progress maps to a customer-defined percentage, and To Do maps to 0%. The customer chooses whether to use MS Project's built-in Status field or PercentComplete based on their reporting needs.

OneDeck

Assignee

maps to

Microsoft Project

Resource Assignment

1:1

Fully supported

OneDeck task assignees map to MS Project resource assignments. We extract the assignee email and display name from OneDeck and match against the destination MS Project resource pool. Resources must be provisioned in MS Project before migration; we generate a resource import template during scoping. Tasks assigned to multiple OneDeck users map to multiple resource assignments on the MS Project task.

OneDeck

Custom Fields

maps to

Microsoft Project

Enterprise Custom Fields

1:1

Mapping required

OneDeck custom fields on tasks (such as priority level, department, cost center, or client name) map to MS Project Enterprise Custom Fields. Field type mapping is required: text fields map to Text custom fields, number fields to Number, date fields to Date. Picklist-style custom fields map to Flag, Number, or Text depending on the destination Project Online or Project Desktop configuration. Custom field availability differs between Task view and Resource view in MS Project; we document which custom fields appear where during the mapping phase.

OneDeck

Views (kanban, table, calendar)

maps to

Microsoft Project

Views

lossy

Fully supported

OneDeck's multiple view types per board do not map directly to MS Project's view model. Kanban columns become grouping fields in MS Project; we configure a custom group-by view to replicate the kanban board feel. Table view maps to the MS Project Sheet view. Calendar view maps to MS Project's Calendar view. The customer receives a view configuration guide documenting the recommended MS Project view equivalent for each OneDeck view, which their PM or admin rebuilds post-migration.

OneDeck

User

maps to

Microsoft Project

Resource

1:1

Fully supported

OneDeck Users map to MS Project Resources. We extract user email addresses and names during discovery and map them to Resource Name and Resource Initials. Resource type (Work, Material, Cost) defaults to Work unless the customer specifies otherwise. If the destination is Project Online, resources are managed in the SharePoint Online admin center or Project Online resource engagement queues.

OneDeck

Documents

maps to

Microsoft Project

Attachments

1:1

Mapping required

OneDeck Document Builder files (quotes, invoices, work orders generated as PDFs) export as file attachments linked to the relevant MS Project task. The PDF content transfers as binary blob; OneDeck-specific formatting (header styles, logo placement, branded layouts) does not survive export. We recommend reviewing a sample of migrated documents post-migration for formatting integrity, particularly for customer-facing documents.

OneDeck

Comments

maps to

Microsoft Project

Task Notes (append)

1:1

Fully supported

OneDeck task comments migrate as timestamped notes appended to the MS Project task's Notes field. Comment author, timestamp, and body concatenate into a formatted text block so that conversation history remains readable. Comment migration is subject to OneDeck plan availability; not all plans expose comment history via API. We verify accessibility during discovery and include comments in scope only when the API exposes them.

OneDeck

Automation Scenarios

maps to

Microsoft Project

Power Automate (rebuild required)

lossy

Not supported

OneDeck Automation Scenarios (trigger-action workflows for record creation, updates, and notifications) do not export in any transferable format. We document every active scenario during scoping: trigger type, conditions, and actions. The customer receives a written automation inventory with recommended Power Automate equivalents. Rebuilding automations in Power Automate is outside standard migration scope and is addressed as a post-migration admin task.

OneDeck	Microsoft Project	Compatibility
Board	Project1:1	Fully supported
Task	Task1:1	Fully supported
Task Status	Task PercentComplete or Status Fieldlossy	Fully supported
Assignee	Resource Assignment1:1	Fully supported
Custom Fields	Enterprise Custom Fields1:1	Mapping required
Views (kanban, table, calendar)	Viewslossy	Fully supported
User	Resource1:1	Fully supported
Documents	Attachments1:1	Mapping required
Comments	Task Notes (append)1:1	Fully supported
Automation Scenarios	Power Automate (rebuild required)lossy	Not 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.

OneDeck gotchas

High

Automation scenarios do not export

Medium

Document PDFs carry OneDeck formatting that may not transfer

Low

Comment history availability varies by plan

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

OneDeck gotchas		Microsoft Project gotchas
Severity	Issue	Severity	Issue
High	Automation scenarios do not export	High	Project for the web is being retired and merged into Microsoft Planner
Medium	Document PDFs carry OneDeck formatting that may not transfer	Medium	Planner-tier portfolio features are incomplete despite Plan 5 labeling
Low	Comment history availability varies by plan	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

Pair-specific challenges

MS Project web version retiring in August 2025

Microsoft announced retirement of Project for the web and the Project and Roadmap apps in Microsoft Teams as of August 2025, redirecting users to Microsoft Planner. Organizations migrating to Microsoft Project must clarify whether they target the desktop application (MS Project Professional or Project Standard) or Project Online (the cloud version). Desktop application data does not sync automatically with Planner. We confirm the destination product family during scoping to avoid migrating into a retiring platform. If the customer requires a Microsoft cloud PM tool, we may recommend Microsoft Planner as the destination instead of MS Project Online.
Task dependencies require manual relationship mapping

OneDeck tasks on a board do not have formal predecessor-successor dependency relationships unless the team used linked subtasks or manual linking features. MS Project's scheduling engine requires explicit Finish-to-Start, Start-to-Start, or other task dependencies to calculate the critical path. We analyze the OneDeck task sequence during scoping, infer likely dependencies from the kanban column progression, and present a dependency mapping proposal to the customer's PM. Without explicit dependency input, tasks migrate as independent activities with no calculated float, which defeats the primary value of MS Project scheduling.
Automation scenarios do not export

OneDeck automation scenarios are defined using platform-specific trigger-action logic tied to its runtime environment. There is no documented export mechanism for these workflows. During migration scoping, we identify every active scenario, capture its trigger conditions and actions in a written inventory, and flag that the customer's team must manually rebuild these automations in Power Automate or document them as standard operating procedures post-migration. This step is frequently underestimated during initial planning and can extend the post-migration stabilization period significantly.
Custom fields behave differently across MS Project views

MS Project custom fields have different availability depending on the view context. Task-level custom fields do not automatically appear in Resource view, and Resource-level custom fields do not appear in Task view. This is a structural difference from OneDeck where custom fields on a record are universally accessible regardless of which view displays the record. We document which custom fields appear in which views during the mapping phase and advise the customer to validate custom field visibility in their actual working views post-migration.
Document PDFs carry OneDeck formatting that may not transfer

The OneDeck Document Builder creates formatted PDFs for quotes, invoices, and work orders. When migrating to MS Project, we export the underlying data fields and binary PDF content as task attachments, but the rendered layout (header, logo, branded formatting) does not survive transfer. We recommend reviewing a sample of migrated documents post-migration to confirm data integrity and flag formatting anomalies before go-live.

Migration approach

Six steps for a successful OneDeck to Microsoft Project data migration

Discovery and destination product clarification

We audit the source OneDeck workspace across all active boards, tasks, subtasks, custom field definitions, user assignments, and document attachments. We also identify automation scenarios that require documentation. Simultaneously, we confirm whether the customer targets MS Project Desktop (Professional/Standard) or Project Online, clarifying that Project for the web retires August 2025. The discovery output is a written migration scope, a task count by board, and a destination product confirmation form signed by the customer's PMO lead.
Dependency analysis and WBS structuring

We analyze task relationships in OneDeck to infer dependency chains. For each board, we map the task sequence and present a dependency mapping proposal: which tasks should have Finish-to-Start relationships, which have concurrent paths, and which are milestones. We design the WBS structure (summary tasks, phases, work packages) aligned with the customer's project breakdown convention. WBS codes are auto-generated during migration based on the agreed structure. This step is critical; migrations that skip dependency design result in MS Project schedules where tasks float freely with no scheduling logic.
Resource pool preparation

We extract all OneDeck users referenced as task assignees and generate a resource import template for MS Project. The customer's MS Project administrator provisions resources in Project Online or the desktop application before migration, matching by email to enable assignment resolution. We validate the resource pool before record import begins and flag any orphaned assignments (OneDeck assignees with no corresponding MS Project resource) for admin resolution.
Sandbox migration and mapping validation

We run a full migration into a test environment using production-like data volume. The customer's project manager reviews 25-50 randomly sampled tasks against the OneDeck source, validates WBS structure and task hierarchy, confirms custom field values and resource assignments, and signs off the mapping before production migration begins. Any corrections to dependency logic, WBS numbering, or custom field mapping happen in this phase.
Production migration in dependency order

We run production migration in record order: resource assignments first (to satisfy the resource pool), then summary tasks and milestones, then detail tasks with WBS numbering and dependency relationships resolved, then custom field values, then document attachments, then comments as appended task notes. Each phase emits a row-count reconciliation report. We use MS Project file import (MPP or MPXJ) for desktop destinations and the Project Online REST API for cloud destinations, with appropriate batch handling and error retry logic.
Cutover, validation, and automation handoff

We freeze OneDeck writes during cutover, run a final delta migration for any records modified during the migration window, then enable MS Project as the system of record. We deliver the automation inventory document to the customer's admin team with Power Automate recommendations. We support a one-week hypercare window for reconciliation issues. We do not rebuild OneDeck automations in Power Automate as part of the standard migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

OneDeck

Source

Strengths

Bundles CRM, project management, sales, and marketing in one workspace reducing tool sprawl
User interface rated highly for ease of use and quick team onboarding across multiple review platforms
Flexible board and view system accommodates kanban, table, and calendar representations of the same data
Document Builder automates quote and invoice generation within the platform workflow
Per-user pricing model scales predictably for small to mid-sized teams

Weaknesses

Automation workflows are not exportable and must be manually rebuilt in destination platforms
Reporting across multiple boards or workspaces requires manual consolidation rather than native cross-board dashboards
Enterprise-grade project portfolio management features lag behind purpose-built PM platforms
Industry-specific workflow templates are limited, often requiring custom configuration

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.

	OneDeck Source	Microsoft Project Destination
Strengths	Bundles CRM, project management, sales, and marketing in one workspace reducing tool sprawl User interface rated highly for ease of use and quick team onboarding across multiple review platforms Flexible board and view system accommodates kanban, table, and calendar representations of the same data Document Builder automates quote and invoice generation within the platform workflow Per-user pricing model scales predictably for small to mid-sized teams	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	Automation workflows are not exportable and must be manually rebuilt in destination platforms Reporting across multiple boards or workspaces requires manual consolidation rather than native cross-board dashboards Enterprise-grade project portfolio management features lag behind purpose-built PM platforms Industry-specific workflow templates are limited, often requiring custom configuration	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 OneDeck 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

OneDeck

Microsoft Project

How OneDeck objects map to Microsoft Project

What specifically takes care here

Six steps for a successful OneDeck to Microsoft Project data migration

Context on both ends of the pair

How hard is this migration?

Estimate your OneDeck to Microsoft Project migration cost

What are you migrating?

Frequently asked questions about OneDeck to Microsoft Project data migrations

Can't find your answer?

Related migrations to explore

Move from OneDeck.
Land in Microsoft Project, intact.

Migrate from OneDeck 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

OneDeck

Microsoft Project

How OneDeck objects map to Microsoft Project

What specifically takes care here

Six steps for a successful OneDeck to Microsoft Project data migration

Context on both ends of the pair

How hard is this migration?

Estimate your OneDeck to Microsoft Project migration cost

Frequently asked questions about OneDeck to Microsoft Project data migrations

Can't find your answer?

How long does a OneDeck to Microsoft Project migration take?

Do OneDeck automation scenarios migrate to MS Project?

What does a OneDeck to Microsoft Project migration typically cost?

Can we migrate to Microsoft Planner instead of MS Project?

Do task comments and attachment history migrate?

How do we handle task dependencies that OneDeck does not model?

What happens to OneDeck custom fields in MS Project?

Is Microsoft Project Online safe to migrate to given the retirement announcement?

Related migrations to explore

Move from OneDeck. Land in Microsoft Project, intact.

Move from OneDeck.
Land in Microsoft Project, intact.