Migrating From DirectAdmin or Plesk to iWebVault

The self-service migration tools are built around cPanel/WHM as the source. But plenty of sites live on DirectAdmin, Plesk, or other panels — and those can move to iWebVault too. The method differs, so this guide explains what to expect when your old host isn’t cPanel.

Why the source panel matters

The single-account and reseller tools talk to a cPanel/WHM source using cPanel’s backup mechanisms. A different panel stores and exports data differently, so the same automated path doesn’t apply directly. That doesn’t mean you’re stuck — it means the migration is handled with a method suited to your source.

The general approach

1. Tell us your source panel (DirectAdmin, Plesk, etc.) and roughly how much data is involved
2. We determine the best export from that panel — its native backup, or a file-plus-database export
3. Your files, databases, and email are brought across to your iWebVault account
4. We verify the migrated site with you before any DNS cutover
5. You point your domain at iWebVault when satisfied

What transfers

The goal is parity: your website files, databases, and email come across, and your site runs the same on iWebVault. Some panel-specific settings don’t have a direct cPanel equivalent and are re-created sensibly on the iWebVault side. We’ll flag anything that needs a decision rather than guessing.

DNS, SSL, and cutover are the same

Regardless of source panel, the cutover experience is identical to any iWebVault migration: verify first, point your domain via nameservers or A record, AutoSSL issues a fresh certificate, and you keep the old account briefly as a fallback. The unfamiliar part is only the export from the old panel, which we handle.

Getting started

Open a ticket noting your source panel and what you’re moving (one site or several). We’ll scope the method, give you a realistic timeline, and either guide you or run the migration for you.

You’re not stuck on a non-cPanel panel

It’s a common worry that leaving DirectAdmin or Plesk means a painful, manual rebuild. It doesn’t. While the self-service tools target cPanel sources, migrations from other panels are a well-trodden path — the difference is in how the data is exported from the source, not in the outcome. Your site ends up running on iWebVault, verified before cutover, just as any migration does.

How non-cPanel sources are handled

Each panel has its own way of packaging an account. The migration uses the most reliable export available for your source — the panel’s native backup where suitable, or a structured export of files plus databases plus email. The pieces are then brought into your iWebVault cPanel account and arranged so your site runs the same.

What carries over

• Website files and document structure
• Databases and their data
• Email accounts and messages
• DNS records, recreated to match

The familiar parts

Once your data is on iWebVault, everything downstream is identical to any migration: you verify the site, point your domain via nameservers or A record, AutoSSL issues a certificate, and you keep the old account as a fallback. The only unfamiliar step — exporting from the non-cPanel source — is the part we handle for you.

Getting started from DirectAdmin or Plesk

1. Open a ticket stating your source panel and what you’re moving
2. We determine the best export method for that panel
3. Your data is brought into your iWebVault account
4. We verify with you, then you cut over when ready

What’s next

• Migrating to iWebVault — How It All Works
• Which Migration Method Is Right for You?
• Verifying a Migration Was Fully Successful

Still stuck? Our team can run or finish the migration for you — open a support ticket and we’ll take it from there.

Key takeaways

The self-service tools target cPanel sources, but migrations from DirectAdmin, Plesk, or other panels are fully supported — the difference is only in how data is exported from the source, not the outcome. Your files, databases, email, and DNS come across, and cutover (verify, point domain, AutoSSL, keep old account) is identical. Open a ticket with your source panel and we’ll handle the export.

Is a non-cPanel migration more risky?

No — the outcome is the same verified result on iWebVault. The only difference is that exporting from a non-cPanel panel isn’t part of the self-service tool, so our team handles that step for you. Everything afterward — verification, cutover, SSL, rollback safety net — works exactly as any migration.

Common mistakes to avoid

• Assuming a non-cPanel site can’t be migrated and rebuilding it by hand
• Trying to force the cPanel self-service tool against a non-cPanel source
• Switching DNS before the migrated site is verified
• Cancelling the old panel account before cutover is confirmed

The key takeaway is that your control panel doesn’t trap you — leaving DirectAdmin or Plesk for iWebVault is a supported, routine move. The export from the old panel is the only specialised step, and our team handles it. Everything downstream is the same verified, low-risk cutover as any cPanel migration.

When to let us handle it

Because the export step from a non-cPanel panel isn’t part of the self-service tools, a migration from DirectAdmin, Plesk, or another panel is something we handle directly — so getting in touch is the natural first move rather than a fallback. Open a ticket noting your source panel and what you’re moving, and we’ll determine the best export method, bring your data across, and verify the result with you before any cutover. You get the same verified, low-risk outcome as a cPanel migration; we simply take care of the one specialised step your old panel requires.