Fix "Something Went Wrong" Microsoft 365 Activation Error on Mac
Question details
The user is unable to activate Microsoft 365 on a new Mac after transferring data from an older MacBook.

- Product
- Microsoft 365 (Word, Excel)
- Device & OS
- macOS Sonoma (MacBook Pro / MacBook Air)
- Scenario
- Migrating data from an old MacBook Pro to a new MacBook Air and attempting to activate the Office suite.
- Observed behavior
- Word and Excel display a "Something went wrong" error message during the Microsoft 365 activation process, preventing the use of the applications.
Ensure you know the email and password for the Microsoft account associated with your active Microsoft 365 subscription, as you will need to sign back in.
Remove Office License Files and Reinstall Microsoft 365
The most effective way to resolve Mac migration activation errors is to clear out conflicting license cache files from both devices and perform a clean installation.
When you use Apple's Migration Assistant to move to a new Mac, older hidden Office license files are often copied over. These files contain hardware-specific identifiers that do not match your new Mac, which directly causes the "Something went wrong" activation failure.
Navigate to the Applications folder on both your old MacBook Pro and your new MacBook Air, and move all Microsoft 365 applications (Word, Excel, PowerPoint) to the Trash.
Download the official Microsoft Office License Removal Tool from the Microsoft support website. Run the pkg file on your new Mac and follow the on-screen prompts to wipe the hidden license cache.
Click the Apple menu and select Restart. This ensures that any background services holding onto the old license data are completely cleared from the system memory.
Go to office.com, sign in with your licensed Microsoft account, and click "Install Office" to download and install a fresh copy of Microsoft 365 on your new MacBook Air.
Launch Word or Excel on the new Mac. When prompted, sign in with the Microsoft account that holds your active subscription to complete the activation process.

Try WPS Office for Mac - No Complex Activation Required
If you are tired of dealing with frustrating Microsoft 365 activation errors, subscription blocks, and license conflicts on your Mac, WPS Office offers a powerful, lightweight, and highly compatible alternative. It works seamlessly on macOS without the hassle of strict license migrations.
- 1. Download the installer: Visit the official WPS Office website and click the "Free Download" button specifically for Mac.
- 2. Install WPS Office: Open the downloaded .dmg file and drag the WPS Office icon into your Applications folder.
- 3. Open your files instantly: Launch WPS Office and directly open your existing Word, Excel, and PowerPoint documents without dealing with activation errors.

Frequently Asked Questions
Why does Mac Migration Assistant cause Office activation errors?
When using Migration Assistant to move data to a new Mac, older hidden Office license files are copied over. These files contain hardware-specific identifiers that do not match your new Mac's hardware, triggering a security mismatch and resulting in the "Something went wrong" error.
Will using the license removal tool delete my Word and Excel documents?
No, the Microsoft Office license removal tool only deletes the hidden activation files located in your Mac's Library folder. Your personal documents, spreadsheets, and presentations are completely safe and will not be touched.
How do I verify if my Microsoft 365 subscription is still active?
You can check your subscription status by logging into your Microsoft account via a web browser and navigating to the "Services & subscriptions" section. Ensure your license is active and in good standing before trying to reactivate Office on your Mac.
Can I use Office on my new Mac without uninstalling it from the old one?
Microsoft 365 does allow you to stay signed in on multiple devices. However, if you are experiencing a persistent activation glitch specifically after a Mac-to-Mac migration, completely removing the license from both devices is the recommended way to clear the backend conflict.




