Cheap License Store — Server Licence Field Notes

Before moving a server licence: a practical IP-change worksheet

Cheap License Store — server licence field notes

Merchant publication by Cheap License Store, prepared with AI assistance. We checked the USD examples against our public catalogue on 16 November 2026. We sell provider-backed IP licences; this is our own operating checklist, not an independent review or a manufacturer partnership statement.

An IP move has at least two questions: where will the software run, and which address will the licence recognise? Treating them as one job makes mistakes harder to untangle. Changing a licence address does not move a database, copy a website or update every network setting. This worksheet keeps the commercial and technical records connected without pretending they are interchangeable.

Make a before-and-after record

Write down the exact product and variant, store service reference, order reference, old public IP and intended new public IP. Add the server nickname, current expiry and the person responsible for the change. Take these details from the actual account and server configuration rather than a remembered screenshot.

Keep a service reference, a software serial key and an installation command in separate fields. Some IP-licensed products do not give the customer a conventional serial key. A visible service identifier is useful for support, but its existence does not make it an activation key. Use the instructions for the actual product and package you purchased.

Check the operation before scheduling the move

Confirm that the product supports an IP change and check the requirements of the destination system. Record the operating system, version and control panel. A similar product name is not proof that another edition, server type or operating system is covered. If the account does not offer the needed operation, resolve the requirement with support rather than assuming a different command will do it.

Prepare a restorable backup, a return plan and an appropriate maintenance window. For an application with changing data, decide how new orders, accounts and edits will be preserved during the move. Test in an isolated environment when possible. The licensing operation is one part of the change, not a substitute for the application's own migration procedure.

Keep a bundle's component list visible

A bundle takes one shared public IP, while its included licences remain separately identifiable components. List each component's status and expiry. One successful component does not establish that the others are ready. If delivery or an update is partial, keep the successful references instead of treating the whole collection as a brand-new purchase.

A shared IP also does not mean multiple hosting control panels can all be installed together on one operating system. Check the actual bundle contents and product compatibility. Do not add a free extra licence or an additional bundle discount to your budget unless the current product terms explicitly include it.

Separate an address change from a paid renewal

Changing an address and extending a paid term are different actions. Before authorising a renewal, check the term, current expiry, renewal total and the preference displayed in your account. Do not infer a new expiry from a checkout success page or from the first-month marketing price alone.

Here is a dated cPanel VPS comparison. These amounts are for the entire selected term:

Months Eligible first order Regular renewal
1 2.10 USD 4.20 USD
3 10.50 USD 12.60 USD
6 23.10 USD 25.20 USD
12 48.30 USD 50.40 USD

The opening offer halves only the first eligible month, once per member for each licence variant. Remaining months and renewals use regular pricing. It cannot be combined with a coupon. Selecting twelve months does not halve all twelve months. Check the final cart amount, applicable tax and renewal conditions before paying. Payment settlement is in USD; a display-currency conversion is a separate presentation choice.

Close the change with evidence

After the supported operation, check the address actually recorded for the service, the real licence status and the displayed expiry. Then test the software and the important application tasks. A dashboard opening successfully is useful, but it is not proof that every user journey or every bundle component works.

If a request times out, first check the existing order and service record. Repeating a purchase without reconciling the earlier result risks making the situation harder to resolve. For support, provide the service reference, product variant, old and new public IP, action attempted, time and exact non-sensitive error. Keep passwords, private API keys and full card details out of public posts and screenshots.

Useful starting points

Current cPanel packages · Public price list · Bundle contents · Installation library · Opening-offer conditions · Contact store support

These notes describe a planning method. The actual supported operation, product limits and current price shown in the store govern a specific purchase. Server rental, managed migration and unlimited storage are not included merely because a licence appears in the price list.