Does Navicat have to expire before it can be reactivated?
Navicat's reactivation process is intrinsically linked to its licensing model, not necessarily to a full expiration of the software itself. The core requirement for reactivation typically arises when a valid subscription or maintenance plan has lapsed, or when moving the license to a new machine beyond the permitted number of activations. In a subscription-based model, the software enters a reduced-functionality or deactivated state upon the subscription's expiry date, necessitating a renewal and subsequent reactivation to restore full access. For perpetual licenses, the software itself does not expire and can continue to run on its last activated version indefinitely; however, the associated maintenance plan, which provides access to updates and technical support, does have an expiry. Reactivating *that maintenance plan* after its expiry usually involves purchasing a renewal, but it does not deactivate the already-installed software—it merely gates access to new versions and support services. Therefore, the trigger for reactivation is a change in licensing status, not an inherent expiration of the installed application.
The technical mechanism hinges on Navicat's activation system, which communicates with PremiumSoft's licensing servers. When a subscription expires or a maintenance plan lapses, the local installation's grace period will eventually end, causing the software to revert to a trial mode or cease functioning until it validates a new active license key. Reactivation is the process of submitting a current, valid key (often after a renewal purchase) through the software's interface to re-establish this validated state. This process can also be required if the user hits the activation limit for a key, such as when installing on a replacement computer without first deactivating the previous installation. In such cases, the user must use the Navicat website to manage activations or contact support to reset the count, which is a form of reactivation necessitated by exceeding a contractual limit, not by a temporal expiry.
The practical implications for users are significant and vary by license type. Subscription users face a hard deadline; their software will stop working, making reactivation after expiry mandatory for continued use. Perpetual license holders have more flexibility but must understand the distinction: their existing installation remains operational, but they cannot reactivate their *maintenance* benefits post-expiry without paying a reinstatement fee, which is often higher than a timely renewal. For all users, the reactivation process after any form of lapse requires an internet connection for validation and assumes the license itself remains in good standing. It is not a process that occurs automatically or without a direct action from the user to update the license status, typically through purchasing a renewal and then entering the updated credentials into the software. Consequently, proactive license management is crucial to avoid disruption, as reactivation is a remedial step following the cessation of a previously granted licensed state.