Endpoint Central License After Moving to a New Server Name or New Server
New hardware, same network, one license. The move itself is simple - as long as you respect the one rule that a license can be applied to only one server.
By Technical AnshuManageEngine Endpoint CentralRead before cutover
Watch the full video - the import you will perform on the new server is the same one shown there.
Server migrations create a licensing tangle only when the license is treated casually - applied here for a test, left running there "just in case". One license, one server is the whole law. This page gives you the cutover order that respects it, and the honest route when a post-move import is rejected.
After a Server Move - License Checklist
License applied on old serverA license works on only one server
New server, same license fileImport it on the new server after cutover
Import rejected after a moveAsk ManageEngine to re-issue for the new server
Both servers live at once on one licenseNot allowed
The license follows your organisation, not the old hardware - but it can only sit on one server at a time.
1
The Rule That Governs Every Move
ManageEngine's FAQ states it without decoration: a license can be applied to only one server. You cannot run the old and new servers side by side on the same license file, and you cannot keep the old box as a warm spare with the same license applied. Every migration plan has to respect that single fact: at cutover, the license comes off the old server's world and goes onto the new one.
2
The Clean Cutover Order
Build and test the new server first using the trial or free mode - get agents talking to it on a small test group.
Schedule the cutover for a quiet window; a license import is quick, but agent redirection takes time to settle.
On the new server, open the console, click the profile icon, select License, and import your existing license file with Enter License File - Upload.
Verify edition, endpoint count and expiry on the new server's License page.
Only then retire or rebuild the old server, so the license lives on exactly one machine.
3
When the Import Refuses on the New Server
Sometimes the file that worked for years is rejected after a move - because the license record is associated with the previous server, or the registered details no longer match the new installation. Retrying the upload will not change the answer. Note the exact error, then contact ManageEngine support or the partner who sold the license, explain that this is a server migration, and ask them to re-issue or re-register the license against the new server. Keep your invoice and the registered email handy; that is how they verify the license is genuinely yours.
A related trap: if you only renamed the server or changed its address, agents may lose contact with it even though the license is fine - that is an agent communication problem, not a licensing one, and it is fixed by pointing agents at the server's stable name or address, not by re-buying anything.
4
What Not to Do During a Migration
Do not apply the license to the new server "just to test" while production still runs on the old one - you have just created a two-servers-one-license conflict.
Do not delete the old server's installation before the new server shows the correct license details.
Do not accept a "replacement license file" from anyone except ManageEngine or your authorised partner.
Watch the Complete Video Guide
For the complete knowledge and full installation walkthrough, watch the full video on the Technical Anshu YouTube channel.
Can I run the old and new servers together on one license during migration?
No. ManageEngine's FAQ is explicit that a license can be applied to only one server. Test the new server in trial or free mode, then apply the license at cutover.
My license file is rejected on the new server. Is the license lost?
No, but the file may be registered against the previous server. Contact ManageEngine support or your authorised partner with your invoice and registered email, explain the migration, and ask for the license to be re-issued for the new server.
We only renamed the server and agents stopped reporting. Is that licensing?
Almost certainly not. A rename or address change breaks agent-to-server communication, while the license itself stays valid. Fix the agents' server reachability; do not buy or re-import licenses for a connectivity problem.
This guide is based on the Technical Anshu video on this topic. Plan the license move as part of the migration checklist, not as an afterthought once agents are already pointing at the new server.