Transferring support contracts after a move means updating each device's registered location and entitlements with every hardware and software vendor, so coverage follows the equipment. Skip it, and four months later a controller fails, someone opens a case, and the vendor's system shows the address you vacated in the spring. Coverage is technically in place and the dispatch goes to the wrong city, which is the same thing as not being covered.
Support entitlements are tied to serial numbers and installation locations in vendor systems that no one updated, because updating them was not on anyone's list. It is administrative work with no visible output, which is precisely why it gets skipped.
Why Does Moving Hardware Affect Support Coverage?
Most enterprise hardware support is priced and delivered against a specific installed address. The service level depends on proximity to a parts depot and a field engineer, and the vendor's dispatch system routes on the address in the record.
Moving a device without updating that record produces several failure modes. Dispatch goes to the old site. Response time commitments quoted for the old location may not be available at the new one, particularly for four-hour service, which requires depot coverage that not every metro has. Where the move crosses a country border, the contract may not extend to the new jurisdiction at all — support agreements are frequently country-specific, and a device shipped from one national entity to another can fall entirely outside its coverage.
Some agreements go further and require notification of relocation as a condition, with the vendor reserving the right to re-inspect equipment or to decline coverage for hardware moved without their involvement. That provision is rarely enforced and it exists, and it is worth knowing about before the argument rather than during it.
When Should You Build the Entitlement Inventory?
Before the move. The work is much easier then than after, because the equipment is in one place and its records are coherent.
For each device: manufacturer, model, serial number, current support contract number, service level, coverage end date, and current registered location. Vendor portals will export most of this. Reconcile it against the asset inventory being built for the move anyway, and the reconciliation itself is informative — it routinely finds equipment in production with no active coverage, coverage being paid on equipment that was decommissioned, and duplicate contracts on the same serial.
Software entitlements need the same treatment, which is why CIS Control 2 treats the software inventory as its own control, and they are easier to lose. Licenses bound to hardware serial numbers, to MAC addresses, or to a host ID break when the hardware changes. Licenses tied to a site or a legal entity may not travel. Subscription entitlements attached to a support contract stop working when the contract lapses, which happens quietly.
Third-party maintenance contracts have their own terms, frequently with tighter relocation provisions than the OEM equivalents, because the provider's economics depend on the parts and engineers they have positioned near the covered site.
When Should You Notify Vendors?
Before the move. The update should happen as part of the move rather than as cleanup.
Notify each vendor in advance with the list of affected serial numbers, the new address, and the planned date. Ask specifically whether the current service level is available at the destination and whether the price changes, because sometimes both do. Ask what documentation they need and how long the change takes to process in their systems.
Where a contract does not cover the destination, that is a procurement action with a lead time, and it should be resolved before the equipment is in production there rather than after.
For software, initiate re-hosting or re-registration ahead of the cutover where the vendor permits it. Some licensing systems allow a license to be staged for a new host; others require the old one to be released first, which creates a gap that has to be scheduled into the outage window rather than discovered inside it.
Verify That It Took
A submitted change request is not a completed one. Vendor systems have processing delays, requests get rejected for mismatched account details, and partial updates are common — the address changes on the account and not on the individual asset records.
Confirm in the vendor portal that each serial number shows the new location and the expected service level. Where the volume makes that impractical, sample it, and sample the most critical devices rather than a random selection.
The definitive test is a real case. Open a low-priority ticket against a relocated device and see where the vendor thinks it is. That takes an hour and it validates the entire chain — entitlement, address, dispatch — in a way that a portal screenshot does not.
Close the Loop on What Left
The other half of the reconciliation is equipment that was retired rather than moved.
Support contracts on decommissioned hardware continue billing until they are cancelled, and organizations routinely pay for coverage on equipment that has been scrapped for years. A decommissioning list run against the entitlement inventory identifies these, and the savings are usually enough to make the whole exercise self-funding.
Cancellation has terms. Some agreements are annual and non-refundable, some allow mid-term removal with credit, and co-terminated contracts covering many assets may require restructuring rather than line-item cancellation. Handle it at renewal where the terms are unfavorable, and make sure the renewal quote reflects the current fleet rather than the fleet from three years ago.
Assign the entitlement reconciliation to a named owner as a closeout deliverable of the migration, with a date. Without that, it belongs to everyone, and the first evidence that it was never done arrives with a failed controller and a field engineer standing outside an empty building.