Migration is included in Enterprise

What we can transfer

Customer accounts, remaining paid time, supported server and key metadata, plans, portal access, DNS settings, and the customer communication needed for the cutover.

How we protect continuity

We build Flirexa in parallel, verify a representative canary, preserve compatible key and address state where possible, and keep a defined rollback point until the result is confirmed.

What needs separate scope

You provide authorized access and an export from the current system. Third-party hosting or provider fees, custom software development, branded applications, and a new marketing website remain separate work.

What Flirexa can help move

Customer records are only one layer

customers, device slots, expiration, and traffic limits
supported WireGuard and AmneziaWG server metadata and key material
subscription plans and remaining access periods
portal accounts and support workflows when a compatible import exists
server locations, DNS settings, and generated configurations
branding and customer-facing legal content for Enterprise

The exact import path depends on the source panel and the quality of its export. A source database dump is not automatically a safe or legally sufficient migration plan.

Canary sizeSmall enough to support manually, broad enough to represent real use

RollbackA documented point before the source is changed, with keys and database state recoverable

CommunicationTell customers what changes, when it changes, and whether a new configuration or app login is required

ReconciliationCompare active access and money-related records before and after cutover