License & Subscription Issues

Move Office 2016 from Subscription to Perpetual Licensing

John WilsonJohn Wilson Nov 20, 2026 870 views

Question details

The user needs a deployment plan to move more than 2,000 computers from an Office 2016 subscription to perpetual licensing while preserving profiles and enterprise settings.

Move Office 2016 from Subscription to Perpetual Licensing
Product
Microsoft Office 2016
Device & OS
not provided
Scenario
An organization is reviewing licensing and deployment options for a large fleet of computers.
Observed behavior
The goal is to deploy and activate a perpetually licensed Office edition while retaining required user profiles and enterprise settings.
Before you start

Inventory the installed Office editions, deployment types, architectures, languages, and activation methods. Confirm the organization's perpetual license entitlements and identify the user and enterprise settings that must be retained.

Solution 1Recommended

Plan and pilot the perpetual-license deployment

Use a tested enterprise deployment plan to validate licensing, installation, activation, and settings before rolling out to the full fleet.

A subscription installation cannot be assumed to convert in place to a perpetual edition. The required removal and installation steps depend on the existing and target editions and their deployment technologies.

Office 2016 support ended on October 14, 2025. Consider a supported Office version and confirm its licensing and deployment requirements before proceeding.

1
Confirm licensing

Review the organization's agreement and Microsoft volume licensing documentation to identify the entitled perpetual edition, installation media, and permitted activation method.

2
Compare installation types

Use the installed-app inventory and Microsoft's deployment documentation to compare the existing subscription installation with the target edition. Determine whether the existing installation must be removed and which deployment tool applies.

3
Document required settings

Review Group Policy, Office configuration settings, add-ins, templates, and user-profile requirements. Record how each setting will be retained or reapplied after installation.

4
Run a pilot

Use Microsoft Configuration Manager, formerly System Center Configuration Manager, or another enterprise deployment tool to deploy the documented removal and installation sequence to a representative test group. Verify activation, profiles, policies, add-ins, and Office files.

5
Roll out in stages

In the deployment tool, expand the tested deployment to staged device groups and monitor installation and activation results. Resolve pilot or deployment failures before moving to the next group.

6
Ask Microsoft for guidance

Post the edition, deployment type, licensing details, and pilot results in a Microsoft Office IT Pro community or contact Microsoft licensing support for guidance on the specific environment.

Plan and pilot the perpetual-license deployment
Verify profile preservation: Retaining a user profile does not guarantee that every Office preference or add-in setting will survive a change of edition. Test the settings that matter to your organization.
Free Microsoft Office alternative

Consider WPS Office as an alternative for everyday productivity

WPS Office is a free, lightweight, easy-to-use alternative with a familiar interface and support for common Microsoft Office formats, helping users transition their everyday documents. It does not change Microsoft Office licensing or activation.

Free tools for everyday document, spreadsheet, and presentation workCompatibility with Microsoft Office formats, including DOCX, XLSX, and PPTXA familiar interface that can ease the move from Microsoft OfficeA lightweight alternative for organizations evaluating productivity software
QA img-9

Frequently Asked Questions

Can I convert an Office 2016 subscription installation directly to a perpetual license?

Do not assume an in-place conversion is supported. Compare the installed and target editions and deployment types in Microsoft's deployment documentation; removal and reinstallation may be required.

Will user profiles and Office settings be preserved?

Preservation depends on the installation change and the settings involved. Test representative profiles, Group Policy settings, templates, and add-ins in a pilot, and document any settings that must be reapplied.

How can I deploy the change to more than 2,000 computers?

Use an enterprise deployment tool such as Microsoft Configuration Manager to deploy a tested installation sequence to staged device groups. Monitor installation and activation results before expanding each stage.

Is Office 2016 still supported?

Office 2016 support ended on October 14, 2025. Review Microsoft's lifecycle documentation and consider a supported Office version before planning a new deployment.

Where can I get help with volume licensing and activation?

Review Microsoft's volume licensing and activation documentation, then contact Microsoft licensing support or post the relevant edition and deployment details in a Microsoft Office IT Pro community.