Flaem

Migrate to Flaem from Pterodactyl, WHMCS, Virtualizor, Convoy or cPanel

A migration moves your clients, services and servers from the old system to the new one. You can move to Flaem from billing systems, game panels, VPS panels and web hosting panels. Every import starts with a dry run and a report, and servers and machines that can stay on their hardware are adopted by Flaem in place.

01How it works

Every import works the same way: a dry run comes first

Whatever the source, the import has the same stages. Nothing is created in the new system until you approve the report.

Pterodactyl import after a dry run: accounts, nodes, eggs, packages and servers, with what cannot move and why
  1. Read

    Flaem reads data from the old system through its API, its database or an account backup.

  2. Dry run report

    You see what will be created, what will change and what cannot be moved.

  3. You approve the report

    Until then nothing changes.

  4. Import

    Accounts, services and machines appear in Flaem. Imports from WHMCS, Convoy and Virtualizor can be rolled back.

  5. Pricing

    Imported plans wait inactive with a price of 0 until you set prices.

  6. New passwords

    Clients set passwords through a reset, because passwords never travel between systems.

02Sources

What moves from each system

Every source has its own importer. Below is exactly what data moves, how the importer reads it and what happens to your clients' services in the meantime.

WHMCS

WHMCS

A billing and hosting automation system.

What moves
  • Clients with their profiles
  • Credit balance into the client wallet
  • Products as plans, once you confirm them
  • Service renewal dates and amounts
  • Invoices as a read-only archive the client can see
  • Saved Stripe cards
How

Read through the API or straight from the database, with read-only queries only. Above 5000 clients the importer reads the database. An applied import can be rolled back.

Client services

The import moves billing data and does not touch servers.

Pterodactyl

A game server panel with the Wings daemon on its nodes.

What moves
  • Users
  • Nodes, as pending until the daemon is switched
  • Port allocations
  • Complete eggs
  • Limits as plans
  • Servers with their identifiers kept
How

Pulled through the panel API. An interrupted import resumes where it stopped.

Client services

A running Wings node is adopted in place: servers and data stay where they are, and only the panel changes.

Pelican

Pelican

A game server panel built on Pterodactyl.

What moves
  • Eggs in the Pelican format
  • Eggs from a file, a URL or a GitHub repository
How

The same egg import as for Pterodactyl, with a field by field preview of each definition before it enters the library.

Client services

Eggs start servers without rewriting, because the Flaem node daemon grows out of Wings.

Convoy

Convoy

A VPS panel on Proxmox.

What moves
  • Virtual machines with the same VMID
  • Users
  • Plans
  • IP addresses
How

Machines are adopted in place, on the same Proxmox. An applied import can be rolled back.

Client services

Machines keep running without a restart.

Virtualizor

Virtualizor

A VPS panel for several virtualisation types.

What moves
  • Machines in Proxmox mode, adopted in place
  • KVM machines, with the disk moved to a Proxmox VE node
How

For KVM machines Flaem moves the disk to a Proxmox VE node during a scheduled maintenance window. An applied import can be rolled back.

Client services

Machines in Proxmox mode run without a restart, and KVM machines move in a window you choose.

SolusVMVirtFusionVMware ESXi

SolusVM, VirtFusion and VMware ESXi

Panels and hypervisors whose machines move to Proxmox VE.

What moves
  • Virtual machines from SolusVM
  • Virtual machines from VirtFusion
  • Virtual machines from VMware ESXi
How

Machines move to Proxmox VE nodes under Flaem, and each one is in the dry run report before anything changes.

Client services

After the move the client manages the machine in the Flaem panel, with browser console, snapshots, ISO images from the catalogue and rescue mode, and pays for it from the same wallet.

cPanelDirectAdmin

cPanel and DirectAdmin

Panels for website and email hosting.

What moves
  • Sites and hostnames
  • Domains and DNS zones
  • Mailboxes, with the password if the backup stores it as a crypt hash
  • Mail forwarders
  • MySQL databases
  • Site files
How

Imported from the backup of a single account. The report states plainly what did not move, for example mailbox contents.

Client services

The import works on an account backup, not on the live server.

03Downtime

Migration without downtime wherever the machine stays in place

When a server or a machine already runs on hardware Flaem supports, only the panel changes. A move is needed only when the machine has to land on Proxmox VE.

VPS monitoring in the client panel: CPU, memory, disk and network every second, percentiles, events on the chart and an active alert

Adopted in place

Servers and machines keep running and the data does not move. Flaem simply takes over control.

old panel
machinerunning
Flaem
  • Wings nodes from Pterodactyl
  • Machines from Convoy, with the same VMID
  • Machines from Virtualizor in Proxmox mode

Moved to Proxmox VE

The machine moves to a Proxmox VE node under Flaem. For KVM machines from Virtualizor you set the time as a maintenance window.

old hypervisor
Proxmox VE
machine
maintenance window
  • KVM machines from Virtualizor
  • Machines from SolusVM, VirtFusion and VMware ESXi

The WHMCS import moves billing data and does not touch servers, and the cPanel and DirectAdmin import works on an account backup, not on the live server.

Once in Flaem, you move VPS and game servers between nodes with a break counted in seconds.

04Pricing

Imported services are not billed until you price them

Every importer creates plans as inactive, with a price of 0. Client services keep running, but Flaem neither bills nor suspends them, so during the move nobody gets an invoice or a suspension by mistake.

  1. 1

    Imported

    Inactive plan with a price of 0. Services run with no invoices and no suspensions.

    no invoices, no suspensions
  2. 2

    Priced

    You set the price and periods. Services from WHMCS keep their renewal dates and amounts.

  3. 3

    Billed

    The service renews from the wallet or a card, and an unpaid one follows the usual suspension path.

05Bridge

Not ready to change billing yet?

Modules for WHMCS, Blesta, HostBill and Paymenter connect Flaem as your service panel, while money and invoices stay in your current system. You run the import later, when you are ready.

Creating, suspending, unsuspending and terminating services and changing plans through the bridge API.

  • WHMCSWHMCSserver module
  • BlestaBlestamodule
  • HostBillHostBillmodule
  • PaymenterPaymenterextension
The billing bridge to WHMCS: option combinations mapped to plans, service states and the latest bridge calls
06Questions

Questions about migration

Your system or question is not here? Tell us what you are moving from and we will check it against your data.

Will my clients' services stop during the migration?

Not where the machine stays in place: Wings nodes from Pterodactyl, machines from Convoy and machines from Virtualizor in Proxmox mode keep running without a restart. KVM machines from Virtualizor move to Proxmox VE in a maintenance window you choose.

Can I roll an import back?

Applied imports from WHMCS, Convoy and Virtualizor can be rolled back. Every import starts with a dry run, so you see the report before anything changes.

What about client passwords?

Passwords never travel between systems. Clients set them through a reset, and their accounts, services and balances are already waiting in Flaem.

When do migrated clients start paying in Flaem?

Once you price the plans. Until then they are inactive with a price of 0, so Flaem bills and suspends nobody. Services from WHMCS keep their renewal dates and amounts.

Can I move machines from VMware ESXi?

Yes. Machines from VMware ESXi, SolusVM and VirtFusion move to Proxmox VE nodes under Flaem, and each one is in the dry run report before anything changes.

My system has no importer on the list. What then?

Tell us what you are moving from and we will check how to move your data. If you use WHMCS, Blesta, HostBill or Paymenter, the bridge module connects Flaem without changing billing.

08Contact

We will plan your migration step by step

Tell us which system you are moving from, how many clients you have and how many nodes. We will show you Flaem and plan the move, from the dry run to the first invoice.