Microsoft 365 Migration

Migrate Word Templates and Add-Ins to Microsoft 365

Phi Hung VoPhi Hung Vo Nov 14, 2026 868 views

Question details

An organization needs to migrate Word 2010 templates, macros, customizations, and add-ins to Microsoft 365.

Migrate Word Templates and Add-Ins to Microsoft 365
Product
Microsoft Word for Microsoft 365
Device & OS
not provided
Scenario
The organization wants to validate existing Word resources before deploying Microsoft 365 to all users.
Observed behavior
The goal is to retain working templates and customizations while identifying compatibility issues in add-ins and code.
Before you start

Inventory the templates, macros, Building Blocks, ribbon customizations, and add-ins users rely on. Identify their storage locations, owners, and any dependencies on Office version or installation paths.

Solution 1Recommended

Pilot and update Word templates and add-ins

Use a pilot installation to find compatibility issues before deploying Microsoft 365 broadly.

Many older Word templates are forward-compatible, but add-ins and custom code should be tested in the actual deployment environment.

1
Set up a pilot

Install Microsoft 365 on one representative computer, then open Word and load the templates and add-ins used in normal work.

2
Test real workflows

Create documents from each template, run macros, insert AutoText and Building Blocks, and test ribbon buttons and third-party add-in commands.

3
Review paths and version checks

Open custom VBA or add-in code and replace hard-coded user or installation paths with appropriate environment variables or other supported location discovery. Update checks limited to Office version 14 to account for Microsoft 365's version 16, or use feature detection where practical.

4
Check add-in compatibility

In Word, open File > Options > Add-ins to review installed add-ins. Confirm with each vendor that its add-in supports the Microsoft 365 version and 32-bit or 64-bit architecture being deployed.

5
Resolve issues before rollout

Correct and retest each issue on the pilot computer, then deploy to additional users only after the required workflows pass.

Pilot and update Word templates and add-ins
Review VBA declarations: Macros that call Windows APIs may need updated declarations, including PtrSafe and appropriate pointer-sized types, for 64-bit Office. Test the revised code in the target environment.
Free Microsoft Office alternative

Explore WPS Office as a Word Alternative

WPS Office is a free, lightweight alternative with a familiar interface for working on documents. Its Microsoft Office format support can help users move everyday files between applications; test specialized templates, macros, and add-ins separately because WPS does not fix Microsoft 365 migration issues.

Open and edit documents in Microsoft Word formats, including DOC and DOCXUse a familiar document-editing interfaceWork with document templates for common tasksMove everyday documents between Office applications with format compatibility
microsoft office alternative - wps office

Frequently Asked Questions

Will my Word 2010 templates work in Microsoft 365?

Many older templates are forward-compatible, but custom macros, paths, and add-ins can still cause problems. Open each template in a pilot installation and test the workflows users depend on.

Can I replace the new Normal.dotm with my old copy?

Avoid overwriting the new Normal.dotm. Use Word's Organizer, Building Blocks tools, and ribbon import/export options to transfer the customizations you need.

Where can I check installed Word add-ins?

Open Word and go to File > Options > Add-ins. Review the list and confirm with each vendor that the add-in supports your Microsoft 365 version and Office architecture.

What should I check in code that detects the Office version?

Look for checks that accept only version 14, which corresponds to Office 2010. Microsoft 365 uses version 16, so update the logic and test it in the pilot environment; feature detection may be more robust where practical.