Office LTSC 2021 End of Support: SMB Migration Plan

Office LTSC 2021, Project LTSC 2021, and Visio LTSC 2021 reach end of support on October 13, 2026. After that date, Microsoft will no longer provide technical support, bug fixes, or security updates for those products. For small and midsize businesses, the practical deadline is earlier: discovery, compatibility testing, purchasing, deployment, and user preparation all need time.

A perpetual license may let a business continue using the software, but it does not make the software perpetually supported. Microsoft’s lifecycle and the license’s use rights are separate. Continuing to run Office 2021 after support ends can therefore leave a company with valid license rights and an increasingly risky, unsupported application estate.

What actually ends in October 2026?

Microsoft’s end-of-support notice covers Office LTSC 2021. Microsoft’s partner guidance also names Project LTSC 2021 and Visio LTSC 2021, all with the same October 13 deadline. Unsupported installations stop receiving security fixes, quality fixes, and assisted technical support. Microsoft recommends Microsoft 365 Apps for most organizations and Office LTSC 2024 where a cloud-connected subscription is not appropriate.

There is a related deadline that deserves its own workstream: Publisher retires in October 2026. Microsoft says Publisher in Microsoft 365 becomes unavailable on October 1, while support for perpetual Publisher ends with Office 2021 on October 13. Businesses should locate .pub files and convert needed material before then. PDF is appropriate for view-only preservation; Word or PowerPoint may be better for content that staff must continue editing.

These dates come directly from Microsoft’s Office LTSC 2021 lifecycle announcement, its April 2026 partner guidance, and the Publisher retirement notice.

Start with an installation and dependency inventory

A purchasing report is not enough. It may show licenses without showing which computers still run the software, who depends on it, or which business processes will break after replacement. Build a device-level inventory and attach an accountable business owner to every exception.

• Device and user: computer name, user, location, operating system, ownership, and whether it is a desktop, laptop, VDI session host, or shared workstation.
• Installed products: Office edition, Project, Visio, Publisher, Access, language packs, architecture, version, build, installation technology, activation type, and current update channel.
• Actual use: last-used evidence and business criticality. Do not buy a Project or Visio replacement for every historic installation without confirming need.
• Dependencies: VBA macros, COM add-ins, templates, fonts, data connections, document-management integrations, PDF tools, label printers, ERP or CRM exports, Outlook plug-ins, and line-of-business applications that automate Office.
• Shared environments: conference-room PCs, call-center workstations, labs, kiosks, Remote Desktop Session Hosts, Windows 365, and other environments where multiple people use the same device.
• Content at risk: Publisher files, Project plans, Visio templates, macro-enabled workbooks, Access databases, custom dictionaries, signatures, templates, and local archives.
• Recovery inputs: deployment package, configuration, product keys or entitlement records where applicable, user settings, content backups, and the prior version removal/reinstall procedure.

Classify each device as migrate, replace, retire, or approved temporary exception. The exception record should state the business reason, compensating controls, owner, deadline, and replacement plan.

Microsoft 365 Apps or Office LTSC 2024?

The right answer can differ by workload. A connected employee laptop and an isolated production workstation do not need the same licensing or update model.

Microsoft’s upgrade planning guidance describes Microsoft 365 Apps as its preferred path and Office LTSC 2024 as the alternative for specific scenarios. The Office LTSC 2024 overview explains the fixed feature model, while Microsoft’s lifecycle record sets the 2029 support end date.

A mixed estate can be appropriate, but it increases operational complexity. Microsoft 365 Apps, Project, and Visio installed on the same computer must meet Microsoft’s compatibility rules for version, installation technology, architecture, and update channel. Standardize those choices in the deployment design rather than letting each device become a one-off configuration.

Handle Project, Visio, and Publisher as separate dependencies

Do not treat Project and Visio as automatic Office components. Determine who creates or edits native files, who only views exports, and which teams use custom templates, macros, stencils, add-ins, or diagrams linked to business systems. Depending on the need, Microsoft points customers toward subscription options such as Planner and Project Plan 3 or Visio Plan 2, or toward Project LTSC 2024 and Visio LTSC 2024 for constrained environments.

Publisher has no direct one-for-one successor. Inventory .pub files by owner and use case, then decide whether each item should become a locked PDF, an editable Word or PowerPoint document, or a redesigned asset in another approved publishing tool. Test print dimensions, fonts, mail-merge behavior, labels, and linked images. Preserve the original file and a conversion log until the business owner approves the result.

Test macros, add-ins, and business workflows

Microsoft notes that Office LTSC 2021 and 2024 share the 16.0 major version and that many existing Group Policy settings and add-ins should continue to work. “Should” is not a production acceptance test. Compatibility depends on the full chain: bitness, security policy, signed code, add-in vendor support, database drivers, network paths, browser controls, and the external systems that exchange data with Office.

Create a workflow-based pilot catalog. Include month-end spreadsheets, estimating and quoting, document generation, mail merge, accounting exports, CRM and ERP integrations, Access applications, Project reporting, Visio automation, document management, PDF creation, printing, and any macro that changes files or sends data. Record expected output and obtain sign-off from the person who owns the process—not only from IT.

Do not overlook shared-device licensing

Microsoft 365 Apps on a shared computer requires a supported plan and Shared Computer Activation. Each user still needs an eligible license and signs in with their own account. Microsoft documents Microsoft 365 Business Premium as the business plan that supports Shared Computer Activation; Business Standard includes desktop apps but does not provide that right. Shared activation tokens also need periodic internet access to renew.

This is a frequent budget and deployment trap. A package that works on a single-user laptop may not be correctly licensed or configured for a shared workstation, VDI host, or Remote Desktop server. Map the device model before selecting subscriptions and validate the design against Microsoft’s Shared Computer Activation guidance.

Choose an update channel deliberately

Microsoft 365 Apps offers Current Channel, Monthly Enterprise Channel, and Semi-Annual Enterprise Channel. Current Channel receives features as they become available; Monthly Enterprise provides a predictable monthly feature schedule. Semi-Annual should not be selected merely because it sounds more stable: Microsoft’s current documentation says changes beginning in July 2026 move that channel toward monthly feature and security servicing.

Choose the channel from business tolerance, add-in testing needs, and support capacity. Use a small validation group before broad release. Keep Office, Project, and Visio on a compatible channel when they share a device. Office LTSC 2024 uses the PerpetualVL2024 channel and receives security and quality updates but not ongoing feature updates. Review Microsoft’s current update-channel guidance and LTSC 2024 update model when finalizing the package.

A practical SMB migration sequence

1. Name a sponsor and fund the work. Separate license cost from engineering, application remediation, training, support, and contingency. Approve procurement early enough to avoid rushed purchasing.
2. Complete discovery. Reconcile device inventory, licensing, usage, dependencies, shared-device scenarios, and business owners. Set a date after which new Office 2021 installations are prohibited.
3. Design the target. Decide Microsoft 365 Apps, LTSC 2024, or a controlled hybrid by device class. Define architecture, channel, identity, activation, policies, telemetry boundaries, and support ownership.
4. Build and test. Package removal and installation with the Office Deployment Tool where applicable. Test files, macros, add-ins, printing, integration, activation, updates, and rollback.
5. Pilot by workflow. Include IT, a normal user, a power user, a shared-device scenario, and owners of critical macros or Project/Visio workflows. Train the pilot group on changed features and support paths.
6. Deploy in rings. Start with low-risk teams, pause for review, then move through increasingly critical groups. Avoid finance close, audit periods, major bids, and other business blackout windows.
7. Close exceptions. Re-scan for Office, Project, Visio, and Publisher 2021. Every remaining installation needs an expiry date, accountable owner, documented controls, and executive acceptance.

Build rollback before deployment

Rollback is not “we still have the old installer.” Define the exact stop conditions: failed activation, broken business add-in, data corruption, printing failure, unacceptable performance, or support-volume threshold. Preserve the prior configuration, tested installation media, entitlement records, user data, templates, and a device list. Back up business content and verify restoration before the change.

Microsoft generally requires the earlier Office installation to be removed before the new product is installed, so long-term side-by-side use is not a safe default. For Monthly Enterprise Channel devices managed through Microsoft’s cloud update controls, Microsoft also documents a limited build rollback capability. That can address a bad Microsoft 365 Apps update; it is not a substitute for a migration-level recovery plan.

If a device must temporarily return to Office 2021 after October 13, treat that state as an emergency exception. Isolate the risk where feasible, set an immediate remediation deadline, and document who accepted it. Rolling back into unsupported software may restore a workflow while increasing security and compliance exposure.

Why delaying creates business risk

• Security: newly discovered vulnerabilities may remain unpatched on affected applications.
• Reliability: a defect or compatibility problem may have no supported vendor fix.
• Operations: urgent migration after a failure costs more and leaves less time for compatibility testing.
• Compliance: unsupported software can conflict with an organization’s patching, vulnerability-management, supplier, or cyber-insurance commitments. The exact impact depends on the applicable contract and control framework.
• Auditability: an incomplete inventory makes it difficult to prove that affected devices were remediated or that exceptions were governed.
• Budget: waiting compresses license purchasing, remediation labor, user support, and project contingency into a smaller window.

The strongest compliance position is evidence, not a verbal assurance: a reconciled inventory, target decision, test results, training records, deployment reports, exception register, and final scan showing what remains.

SMB leadership checklist

• Assign an executive sponsor, technical owner, and budget owner.
• Inventory Office, Project, Visio, and Publisher 2021 by device and actual use.
• Choose Microsoft 365 Apps or LTSC 2024 by workload—not by habit.
• Resolve shared-device, VDI, and Remote Desktop licensing before purchasing.
• Convert required Publisher files and validate their output.
• Test macros, add-ins, templates, data connections, printing, and integrations.
• Select and govern update channels.
• Pilot with real workflows, train users, and staff the help desk.
• Deploy in rings with explicit stop and rollback criteria.
• Re-scan, close gaps, and give every temporary exception an owner and expiry date.

Primary Microsoft sources

• Office LTSC 2021 end of support
• Microsoft Partner Center announcements, April 2026
• Microsoft Publisher retirement guidance
• Plan an upgrade from older Office versions
• Office LTSC 2024 overview
• Shared Computer Activation overview
• Microsoft 365 Apps update channels

Lifecycle, licensing, and product guidance can change. Validate the final licensing and deployment design against current Microsoft documentation and your organization’s agreements before purchasing or implementation.