MIGRATING FROM LEGACY LICENSING SYSTEMS

SLASCONE includes several features designed to make migrating from an existing licensing system as smooth as possible.

Imagine you’re a software vendor with 1000 active licenses. Beginning with your next release (e.g., version 7.0), you want all licensing to be handled by SLASCONE.

Of course, manually recreating all existing customer and license records in SLASCONE isn’t feasible. You also want to avoid issuing and sending new license codes to customers who upgrade to version 7.0. So how can you migrate without disrupting your users?

• Bulk import and synchronization via API
  The SLASCONE API lets you bulk import your existing customer and license data.

• Legacy key mapping during license creation/import
  When you create or import a license, you can store the existing (“legacy”) license key alongside the new SLASCONE license key. This creates a mapping such as:

  • SLASCONE key: 1c7bd779-bf7e-461d-8412-f2ba287d3bc6

  • Legacy key: 24204-43534-23453-57856

• Activation behavior in version 7.0
  On the first run of version 7.0:

  • Upgrade from an earlier version: the product activates using the legacy key.

  • New installation: the product activates using the SLASCONE key.

• After the first activation
  All subsequent licensing requests are made using the SLASCONE key.

This approach enables a seamless migration: existing customers can upgrade without changing their license codes, while new installations immediately use SLASCONE-native licensing.