Migrate your Project Central data
A Microsoft 365-native project management tool with unlimited users, a clean interface, and per-user pricing that serves small to mid-market teams.
In its favor
Why people choose Project Central
The signal that keeps Project Central on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Project Central requires zero new tool adoption for Microsoft 365 teams — the interface and sign-in are already familiar, which reduces friction and drives daily active usage across non-technical team members.
The clean, uncluttered UI makes project progress and status visible at a glance, which managers cite as the primary reason their teams actually use it consistently rather than abandoning it.
Deep integration with Outlook, Teams, and SharePoint means task updates, due dates, and project context surface where teams already work, rather than requiring a separate application open.
Small businesses and mid-market teams report quick time-to-value because the tool does not require a dedicated project management expert to configure or maintain it effectively.
The platform supports both Agile and Waterfall methodologies with customizable templates and workflows, making it adaptable to diverse team structures without forcing a single project framework.
Organizations without an existing Microsoft 365 license cannot use Project Central at all, making it a non-starter for teams on Google Workspace or other ecosystems without first purchasing a Microsoft subscription.
Per-user pricing scales linearly with headcount, which becomes a budget concern as project portfolios grow and organizations need to expand access to more stakeholders and contractors.
The platform is not designed for enterprise-scale resource management or advanced portfolio analytics, so growing teams often outpace what Project Central can offer in reporting depth.
Reasons to switch
Why people leave Project Central
The recurring reasons buyers give for replacing Project Central. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Project Central fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Project Central pricing overview
Project Central uses a per-user, per-month pricing model with a 14-day free trial requiring an active Microsoft 365 license. The platform offers unlimited users across all paid tiers, with dedicated customer success management and onboarding sessions included. Specific tier pricing amounts are not published on the vendor website and require direct inquiry.
Annual
Tier 1 of 2
$49/month (billed annually) — 25% discount vs monthly per projectcentral.com/pricing
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Project Central's schedule — see our quote-based pricing →
What gets migrated
Project Central object support
Object-by-object support for Project Central migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Project Central with name, description, status, owner, dates, and assigned team. We export Projects 1:1 to the destination PM tool's project or workspace object.
Tasks
Fully supportedTasks belong to Projects and carry title, description, status, due date, assignee, checklist items, and comments. We preserve task-to-project linkage and the parent-child structure when subtasks exist.
Subtasks
Mapping requiredProject Central uses checklist items inside tasks rather than first-class subtasks. We convert checklist items to subtasks in the destination where possible, or preserve them as checklist data on the parent task.
Assignees
Fully supportedAssignees are Microsoft 365 users from the customer's tenant. We map assignee identities by Azure AD object ID or UPN to the destination user system.
Comments
Fully supportedComments on tasks export with author, timestamp, and body text. We preserve comment ordering and author attribution on the destination.
Attachments
Mapping requiredProject Central does not store native file attachments — files live in SharePoint and Project Central holds URL references. We migrate the SharePoint link as a custom URL field rather than copying file bytes.
Custom Fields
Mapping requiredCustom fields on tasks and projects export as name/value pairs. We map each to a compatible destination property; type mismatches (text vs picklist vs date) are reconciled during scoping.
Dependencies
Mapping requiredTask dependencies (predecessor/successor) export when the Gantt view is in use. We preserve the dependency graph; circular dependencies are flagged for customer review before import.
Views
Mapping requiredProject Central supports list, board, and Gantt views per project. View configurations are platform-specific and rebuilt at the destination; underlying task data carries over.
Activity Feed
Mapping requiredActivity feed entries (status changes, assignment changes) are derived audit records. We export the activity stream as a timeline of events linked to the relevant project or task; some destinations cannot ingest these directly.
Status Reports
Mapping requiredStatus report definitions are configurable per project. We export current status report content but rebuild report templates in the destination since report engines differ across platforms.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Project Central with name, description, status, owner, dates, and assigned team. We export Projects 1:1 to the destination PM tool's project or workspace object. |
| Tasks | Fully supported | Tasks belong to Projects and carry title, description, status, due date, assignee, checklist items, and comments. We preserve task-to-project linkage and the parent-child structure when subtasks exist. |
| Subtasks | Mapping required | Project Central uses checklist items inside tasks rather than first-class subtasks. We convert checklist items to subtasks in the destination where possible, or preserve them as checklist data on the parent task. |
| Assignees | Fully supported | Assignees are Microsoft 365 users from the customer's tenant. We map assignee identities by Azure AD object ID or UPN to the destination user system. |
| Comments | Fully supported | Comments on tasks export with author, timestamp, and body text. We preserve comment ordering and author attribution on the destination. |
| Attachments | Mapping required | Project Central does not store native file attachments — files live in SharePoint and Project Central holds URL references. We migrate the SharePoint link as a custom URL field rather than copying file bytes. |
| Custom Fields | Mapping required | Custom fields on tasks and projects export as name/value pairs. We map each to a compatible destination property; type mismatches (text vs picklist vs date) are reconciled during scoping. |
| Dependencies | Mapping required | Task dependencies (predecessor/successor) export when the Gantt view is in use. We preserve the dependency graph; circular dependencies are flagged for customer review before import. |
| Views | Mapping required | Project Central supports list, board, and Gantt views per project. View configurations are platform-specific and rebuilt at the destination; underlying task data carries over. |
| Activity Feed | Mapping required | Activity feed entries (status changes, assignment changes) are derived audit records. We export the activity stream as a timeline of events linked to the relevant project or task; some destinations cannot ingest these directly. |
| Status Reports | Mapping required | Status report definitions are configurable per project. We export current status report content but rebuild report templates in the destination since report engines differ across platforms. |
Gotchas
What to watch for in Project Central migrations
Issues we've hit on past Project Central migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Microsoft 365 license is a hard prerequisite
Attachments are SharePoint links only — files are not duplicated in Project Central
No public API or developer portal — extraction is UI/CSV-driven
Pricing model is flat $49/month for unlimited users, not per-user as commonly assumed
Project Online migration timing — Microsoft sunset in September 2026
| Severity | Issue |
|---|---|
| High | Microsoft 365 license is a hard prerequisite |
| High | Attachments are SharePoint links only — files are not duplicated in Project Central |
| High | No public API or developer portal — extraction is UI/CSV-driven |
| Medium | Pricing model is flat $49/month for unlimited users, not per-user as commonly assumed |
| Medium | Project Online migration timing — Microsoft sunset in September 2026 |
Leaving Project Central?
Where Project Central customers move next
5 destinations Project Central can migrate to.
How a Project Central migration works
Four steps, Project Central-specific
Connect
Not publicly documented into Project Central. Scopes limited to read-only on the data we move.
Map
We translate Project Central-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Project Central quirks before production.
Migrate
Full migration with Project Central rate-limit handling. Rollback available throughout.
FAQ
Project Central migration FAQ
Answers to the questions buyers ask most during Project Central migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Project Central migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Project Central.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Project Central setup and destination — written quote back within a business day.