Automatic migration of products and account-based Composer Access Keys

We will begin the deprecation of account-based Composer keys on January 1, 2026.

To help customers maintain uninterrupted access to their Amasty products and minimize potential issues, Amasty will perform an automatic migration of unassigned products and account-based Composer keys into projects.

This migration ensures that all licenses remain accessible through project-based Composer keys, which will be the only supported method moving forward.

Who will be included in automatic migration?

The automatic migration will only apply to two types of accounts:

1. Accounts without any projects

For these accounts, we will:

• Automatically create a new project  with a clearly identifiable, generic name.

• Assign all unassigned products into this new project.

• Migrate all existing account-based Composer access keys into the same project.

As a result, all your products and access keys will be grouped under one project to ensure continued access once account-based keys are disabled.

2. Accounts with a single existing project

For these accounts, Amasty will:

• Move all unassigned products into the existing project.

• Migrate all existing account-based Composer access keys into this project as well.

After the migration, all modules and keys will be managed within that project.
We recommend checking your project setup afterward to ensure that all products are correctly assigned.

Note: If you prefer to organize your products differently, you can create a new project and reassign modules manually. In this case, don’t forget to generate and start using the in-project Composer keys from your new project

Who will not be included in automatic migration?

Accounts with multiple projects will not be included in the automatic migration.

These customers should continue to manage their product assignments and Composer keys manually to ensure proper setup and uninterrupted access.

When will the migration take place?

The automatic migration is planned for early 2026. All affected customers will receive a notification once the migration is complete.

What do I need to do?

If your account falls under the automatic migration criteria, no immediate action is required on your part.

However, after the migration, we recommend:

• Review your project(s) in your Amasty account.

• Confirm that products and access keys are assigned as expected.

• Start using in-project Composer keys for all installations.

If your account has multiple projects, please manage product assignments manually before January 1, 2026, to avoid access interruptions.