Can You Move a Licence to a New PC? Transfer and Reassignment Rules

Fix it now

Whether a licence can follow a user depends on how it was bought. Subscriptions are assigned to people and move freely. Server licences and CALs may be reassigned, but the Product Terms say not less than 90 days since the last reassignment of that same licence. Desktop transferability is decided by channel, and the first thing to do is find out which channel you actually hold.

1. Run slmgr /dli in an elevated Command Prompt and read the description. It tells you the channel, which answers the transferability question before you spend anything.
2. Link the digital licence to a Microsoft account before you change any hardware. The activation troubleshooter needs that link to already exist.
3. Reassign Microsoft 365 seats freely. They are assigned per user and there is no waiting period.
4. Apply the 90-day rule to server licences and CALs, and use the exceptions where they apply: permanent hardware failure or loss, termination of the user’s employment or contract, and temporary reallocation of CALs.
5. For virtual machines that move between hosts, check whether your licences carry Software Assurance or are subscription licences, because that is what permits frequent reassignment within a server farm.
6. Read the licence terms supplied with a preinstalled machine before assuming its Windows licence can move.

If slmgr reports a retail or volume channel and the licence is linked to a Microsoft account, stop here: it moves. Below are the reassignment rules in full and what to do when activation refuses.

Why it happens

There are two different questions hiding inside ‘can I move this licence’, and mixing them up is what produces bad advice. One is about desktop software and the channel it was sold through. The other is about server-side licences and a timing rule in the Product Terms.

On the server side the rule is published and short. A customer may reassign a licence to another device or user, but not less than 90 days since the last reassignment of that same licence. The purpose is to stop a small pool of licences being shuffled around to cover a much larger population.

There are three named exceptions, and they cover most of what organisations actually need: permanent hardware failure or loss, termination of the user’s employment or contract, and temporary reallocation of CALs. A server that has died and been replaced, and a member of staff who has left, both fall outside the waiting period. Moving a licence between two working servers every fortnight to follow a workload does not.

Subscription licences sidestep all of this because they are not attached to hardware at all. A Microsoft 365 seat is assigned to a person, that person installs on the devices their plan permits, and you can deactivate an install from the account portal at any time. When somebody leaves, you reassign the seat, which is straightforward and expected.

Full reference

What moves, and on what terms

Read the licence terms supplied with the specific product rather than a general summary. Microsoft publishes the applicable Software Licence Terms by product, version and distribution channel – preinstalled from a manufacturer versus packaged software – and the transferability answer lives in that document rather than in a rule of thumb.

The 90-day rule and its exceptions, stated exactly

The Product Terms permit reassignment of a licence to another device or user, but not less than 90 days since the last reassignment of that same licence. Reassignment sooner than that is permitted where it is due to permanent hardware failure or loss, termination of the user’s employment or contract, or temporary reallocation of CALs.

Two practical readings follow. First, the clock is per licence, not per server or per person, so a licence reassigned yesterday is locked for 90 days regardless of what happens to the machine it came from. Second, the exceptions are about events rather than convenience: a failed server, a leaver, and short-term CAL movement. Rotating licences around a healthy estate to cover more users than you have bought is exactly what the clause exists to prevent, and it is also what a licence review looks for.

Hardware changes on a single PC

1. Before making any hardware change, confirm you are signed in with a Microsoft account and that Settings, System, Activation shows the digital licence linked to that account.
2. Make the hardware change.
3. If Windows reports that it is not activated, open Settings, System, Activation and run Troubleshoot.
4. Choose the option indicating you changed hardware on this device recently, sign in, and select the device from the list.
5. If no linked digital licence exists, use Change product key on the same page and enter the key you hold.
6. Where the licence is retail and the automated check declines a legitimate change, telephone activation via slui 4 is the documented fallback.

The activation troubleshooter only recovers a licence that was already linked to a Microsoft account before the change. It cannot create an entitlement that does not exist, so it will not move a licence that is bound to the original hardware under its supplied terms.

slmgr /dli
slmgr /dlv
slui 4

People, not machines

When somebody leaves, deal with the mailbox before the licence. Convert it to a shared mailbox or delegate access first, then remove the licence from the departing account, then assign the seat to their replacement. There is no waiting period for subscription seats, and the sequence matters only because removing a licence before handling the mailbox creates avoidable work.

On the server side, the departure of a licensed user is one of the three named exceptions to the 90-day rule, so a CAL assigned to a leaver can be reassigned immediately. Keep a record of the reassignment and its reason, because that record is what makes the exception demonstrable later.

Which route applies to you

• New PC replacing an old one that came with Windows preinstalled: read the terms supplied with the original machine before assuming anything, and budget for a licence on the new one.
• New PC replacing an old one activated with a retail key: transfer it. Remove it from the old machine, then activate on the new one, using telephone activation if the online check declines.
• Employee leaves and is replaced: reassign the Microsoft 365 seat immediately, after converting or delegating the mailbox.
• Server failed permanently and has been replaced: reassign immediately. Permanent hardware failure is an explicit exception to the waiting period.
• Moving a workload between two healthy servers regularly: this is where the 90-day rule bites, and Software Assurance or subscription licensing within a server farm is the mechanism that removes the problem.
• Buying a business that owns volume licences: transfers between legal entities go through Microsoft’s licence transfer process. Take advice before relying on it.

Questions people ask about this