In development

QuroPanel is under active development. Follow the roadmap and join the first public testing group.

View roadmap Development updates
QuroPanel
Follow development
Platform overviewAll featuresIntegrationsQuroAdminQuroResellerQuroControlQuroCommerceQuroDeployQuroShieldQuroSupportNative appsQuroDeskQuroCLI
Hosting providersResellersAgenciesDevelopersWordPress hostingApplication hostingMigrating inCompare panels
Why open sourceLicenceContributeRoadmapSecurity overviewArchitectureResponsible disclosureRelease signing
Download and installSystem requirementsDocumentationMigration guideDevelopment updatesChangelogCommunityBrand and press
Pricing
Follow development

Migration

Move your data without rebuilding the business by hand

Migration tooling is planned for hosting accounts, customers, services, domains, invoices, tickets and application data.

Planned sources

cPanel & WHM

Accounts, domains, DNS, databases, mail, SSL, cron and file data from a WHM server or a cPanel account backup.

Planned

WHMCS

Customers, products, services, domains, invoices, transactions, tickets and email templates from your own authorised database or export.

Planned

DirectAdmin

User, reseller and admin level accounts with their domains, databases and mail.

Planned

Plesk

Subscriptions, domains, databases, mail and the associated file data.

Planned

aaPanel

Sites, databases, FTP accounts, cron jobs and SSL certificates.

Planned

FOSSBilling

Clients, orders, invoices, products and support tickets.

Planned

Paymenter

Clients, products, services and invoices.

Planned

Generic Linux

A server with no panel: file data, databases, mail and DNS discovered directly.

Planned

CSV or API

A mapped import for anything the built-in readers do not cover.

Planned

How a migration will run

Nothing moves until a dry run has reported what would happen.

1Connect source
2Discover accounts
3Compatibility report
4Dry run
5Initial copy
6Delta sync
7Validate
8DNS cutover
9Rollback window

What the compatibility report will flag

  • PHP versions and missing extensions
  • Apache rewrite rules with no Nginx equivalent
  • Database engine and version differences
  • Mailbox sizes and unsupported mail features
  • DNS records that will not survive the move
  • Custom services, symlinks and file ownership
  • Node and Python applications and their runtimes

On boundaries: imports read only from data you own and are authorised to access. No commercial panel's code is copied, no encrypted secret is bypassed, and no attempt is made to decrypt existing payment gateway tokens — those have to be reconnected through the provider.

Follow the build

The roadmap shows what is specified, what is being built and what is still only planned.

View the roadmap

Contribute

Drivers, integrations, translations and documentation are all places to start.

How to contribute

Report a security issue

Responsible disclosure, with a stated response commitment.

Disclosure policy