If you're using the native Shopware PaaS platform, this article is for you.
Starting July 06, 2026, authentication for the native Shopware PaaS platform will transition to Shopware Account.
This change makes onboarding new users easier, simplifies account management, and provides a more consistent login experience across Shopware services.
Who is affected?
This migration applies only to customers using the native Shopware PaaS platform.
Customers using Shopware PaaS powered by Upsun are not affected.
Why are we making this change?
Our goal is simple: make getting started with Shopware PaaS faster, easier, and more reliable.
Today, accessing the native Shopware PaaS platform requires a dedicated PaaS account in addition to a Shopware Account. Every new user currently needs to be onboarded manually by Shopware before they can start using the platform.
While this process has served us well, it doesn't scale as organizations grow.
By moving authentication to Shopware Account, we're giving organizations more control over user management while providing a smoother onboarding experience.
What's changing?
Simplified onboarding
Starting with the new CLI release:
New users can create their own Shopware Account.
Organization administrators can invite colleagues directly.
Organization administrators can assign non-admin roles themselves.
Shopware will continue to manage Admin role assignments.
This removes one of the biggest onboarding bottlenecks: waiting for Shopware to manually create user accounts.
A single login across Shopware services
Instead of maintaining a separate PaaS account, users will authenticate using their Shopware Account.
This provides:
A more consistent login experience
Easier account management
Less administrative overhead
Faster onboarding for new team members
What does this mean for existing users?
If you're already using the native Shopware PaaS platform, you'll need to migrate your existing PaaS account to your Shopware Account.
For most users, the migration will be seamless.
If your Shopware Account uses the same email address as your existing PaaS account, your:
Organization memberships
Project access
Application permissions
Roles
will be transferred automatically the first time you sign in.
If you're using a different email address, your organization administrator or Shopware Support can grant your Shopware Account access to the appropriate organization.
Using CI/CD or deployment automation?
If you use Personal Access Tokens (PATs) for:
CI/CD pipelines
Deployment automation
Scripts
Integrations
there is one important change to be aware of.
Existing Personal Access Tokens remain valid until your first login with Shopware Account.
After your first login:
Existing Personal Access Tokens become invalid.
You'll need to create a new Personal Access Token or, preferably, migrate to a Service Account.
We recommend using Service Accounts for automation because they belong to your organization rather than an individual user and are designed for long-running automation and CI/CD workflows.
For setup instructions and additional details, refer to the documentation.
Migration Timeline
06 July 2026
A new version of the sw-paas CLI will be released.
With this release:
Shopware Account authentication becomes available.
Existing users can start migrating.
New users will onboard through Shopware Account.
06 July – 02 August 2026
Migration window.
During this period:
Existing authentication continues to work.
Existing users should migrate to Shopware Account.
We recommend completing the migration as early as possible.
03 August 2026
The migration is complete.
From this date:
Shopware Account becomes the only supported authentication method.
Legacy PaaS accounts can no longer be used.
The previous CLI authentication flow is no longer supported.
What do I need to do?
Existing users
Before 02 August 2026:
Create a Shopware Account if you don't already have one.
Ensure your Shopware Account uses the same email address as your existing PaaS account whenever possible.
Complete your first login using Shopware Account.
Update to the latest
sw-paasCLI.
If your Shopware Account uses a different email address, please contact your organization administrator or Shopware Support before the migration deadline.
New users
Starting 06 July 2026, onboarding becomes much simpler.
Simply:
Create a Shopware Account.
Ask your organization administrator to grant access to the appropriate organization.
Install the latest
sw-paasCLI.
There's no longer a need to wait for Shopware to create a dedicated PaaS account.
Frequently Asked Questions
What happens if I don't migrate before 03 August?
After 03 August 2026, legacy authentication will no longer be available.
You'll need to complete your migration before you can access the native Shopware PaaS platform again.
What happens to my projects and permissions?
If your Shopware Account uses the same email address as your existing PaaS account, your organization memberships, project access, application permissions, and roles are transferred automatically during your first login. Your existing organizations, projects and applications are not affected in any way.
What if my Shopware Account uses a different email address?
Automatic migration is only possible when the email addresses match.
If they don't, ask your organization administrator to invite your Shopware Account or contact Shopware Support for assistance.
Do I need to update the CLI?
Yes.
The new authentication flow requires the latest version of the sw-paas CLI.
We recommend completing your account migration before updating.
Will my deployments be affected?
If you use Personal Access Tokens for automation, you may need to update your authentication after migrating.
We recommend moving long-running automation to Service Accounts.
Learn more about Service Accounts.
Need help?
If you have questions or experience any issues during the migration, our Support team is happy to help.
We'll also continue to update this article with additional guidance and answers to common questions throughout the migration period.
