Project 2016 & 2019 End of Support: Upgrade Guide

Microsoft ended support for Project 2016 and Project 2019 on October 14, 2025. The applications may still open and run, but Microsoft no longer provides routine security fixes, bug fixes or technical support for these versions.

If your organization still relies on either release, now is the time to review your project files, add-ins and deployment setup before moving to a supported version. For most perpetual-license users, the clearest upgrade options are Project 2024 Professional and Project LTSC 2024 Professional.

Project 2016 and 2019 End-of-Support Dates

What Does End of Support Mean for Microsoft Project?

End of support does not deactivate the software or automatically delete your project files. It means Microsoft has ended the normal support lifecycle for that version.

Project 2016 and Project 2019 no longer receive:

• Routine security fixes for newly discovered vulnerabilities
• Bug fixes for newly identified software issues
• Compatibility improvements for newer operating systems and connected services
• Standard technical support from Microsoft

The software may continue working, but the risk profile changes. A problem that appears after support ends may remain unresolved, particularly when it involves a newer Windows update, an add-in, a connected service or an organization-specific security requirement.

Can You Still Use Project 2016 or Project 2019?

Yes, but continued use is not recommended for business-critical work. Existing installations are not automatically switched off when support ends. However, using unsupported software can make it harder to maintain a secure, compliant and reliable working environment.

The level of urgency depends on how Project is used. A standalone home computer presents a different risk from a company device connected to shared storage, Microsoft services, customer data or regulated business systems. Organizations should treat unsupported Project installations as part of their wider software-risk assessment.

Why Upgrade from Project 2016 or 2019?

1. Reduce Exposure to Unpatched Issues

Once a version is unsupported, newly discovered vulnerabilities may not receive a fix. The longer an unsupported application remains in use, the more difficult it becomes to manage that uncertainty through ordinary patching.

2. Improve Compatibility with a Modern Windows Environment

New hardware, operating-system updates, security controls and connected services are tested primarily against supported software. Moving to Project 2024 reduces reliance on a legacy application stack and gives IT teams a cleaner foundation for future updates.

3. Maintain Access to Vendor Support

When a problem affects project files, printing, integrations or deployment, vendor support can be crucial. Unsupported versions leave organizations with fewer escalation options and a greater dependence on internal troubleshooting.

4. Simplify Compliance and Software Governance

Many security frameworks require organizations to maintain supported software. Keeping Project 2016 or 2019 in production may create audit questions, exceptions or additional compensating controls.

5. Avoid a Rushed Migration Later

Project files may contain custom fields, macros, templates, reports and links to external resources. A planned migration gives you time to test these elements instead of discovering problems during an urgent replacement.

Which Project 2024 Edition Should You Choose?

Project Professional 2024

Project Professional 2024 is a perpetual desktop edition for users who want to manage schedules, resources, costs and project reporting without an ongoing Project subscription. It follows Microsoft’s Modern Lifecycle Policy and is supported until October 9, 2029.

Project LTSC 2024 Professional

Project LTSC 2024 Professional is designed for organizations that favor a fixed feature set, controlled deployment and predictable servicing. It follows Microsoft’s Fixed Lifecycle Policy and is also supported until October 9, 2029.

For a detailed side-by-side comparison of licensing, servicing, deployment and ideal use cases, read our Project LTSC 2024 vs non-LTSC Project 2024 comparison.

What Does Project Professional 2024 Include?

Project Professional 2024 retains the familiar desktop approach while providing a currently supported platform for project planning. Key capabilities include:

• Pre-built templates to speed up project setup
• Automated scheduling based on task dependencies
• Resource-management tools for assigning people and reviewing workloads
• What-if scenarios for evaluating task assignments
• Built-in reports such as Burndown and Resource Overview
• Multiple timelines for presenting complex schedules more clearly
• Task-path highlighting for understanding relationships in Gantt charts
• Timesheets for recording project and non-project work
• Project Online and Project Server synchronization where the required services and licenses are available

Some collaboration features depend on separately licensed Microsoft services. Check the licensing requirements for your intended workflow rather than assuming every cloud feature is included with the desktop license.

Project 2016 vs Project 2019 vs Project 2024

The strongest reason to move from Project 2016 or 2019 is not a single headline feature. It is the combination of current support, security maintenance and compatibility with a modern software environment.

Should You Upgrade to Windows 11 at the Same Time?

Project Professional 2024 can run on supported Windows configurations, but organizations still using standard Windows 10 Home or Pro should note that Windows 10 itself reached end of support on October 14, 2025.

Moving to Windows 11 can therefore help create a more complete supported environment rather than replacing one unsupported application while leaving the operating system behind.

Before upgrading, confirm that each device meets the Windows 11 hardware requirements and that business-critical drivers, add-ins and peripherals are compatible.

How to Upgrade from Project 2016 or 2019

1. Inventory Your Current Installation

   Record the Project edition, version, bitness, installation type, license arrangement and number of devices in use.

2. Back Up Project Data

   Save copies of important .mpp files, global templates, macros, custom reports, views, calendars and resource pools.

3. Check Add-ins and Integrations

   Identify connections to Excel, SharePoint, Project Server, accounting tools, reporting platforms and third-party add-ins.

4. Choose the Right Project 2024 Edition

   Select Project Professional 2024 for a current perpetual desktop release or Project LTSC 2024 Professional for a more controlled, fixed-feature deployment model.

5. Review Office and Windows Compatibility

   Check 32-bit or 64-bit architecture, installation technology, deployment channel and operating-system support before installing the new version.

6. Run a Pilot Deployment

   Test the upgrade with representative project files and workflows before rolling it out to every user.

7. Validate Files After Migration

   Open key projects and review dates, dependencies, formulas, resource assignments, reports and print layouts.

8. Document the New Environment

   Record installation details, license information, support contacts and any changes users need to know.

Office 2019 Has Also Reached End of Support

Office 2019 reached end of support on the same date as Project 2019: October 14, 2025. If both products are installed in your environment, reviewing them together can reduce deployment conflicts and prevent a second migration project later.

Explore the available Office 2024 editions and confirm the complete Office, Project and Windows configuration before deployment.

Move to a Supported Project Platform

Project 2016 and Project 2019 have passed their support deadline. Continuing to rely on them may increase security, compatibility and governance risks, particularly in business environments.

A carefully tested move to Project 2024 provides a supported foundation while preserving the familiar desktop planning workflow many users depend on.