Other sources
Static sites: Git and archives
Section titled “Static sites: Git and archives”For a static site (plain HTML, or the output of a static site generator), create a Static site and import it from:
- A Git repository — give it the repository URL and, for a private repository, credentials or a deploy key. OPanel checks out the repository into the site.
- An archive — upload a
.zipor.tar.gzof the site’s files directly. - SFTP/FTP pull — give it an existing host’s address and credentials and let it pull the files across, similar to a WordPress SSH migration.
As with WordPress migrations, any address you give as a source is checked and only public internet addresses are accepted — nothing on your provider’s own network can be targeted this way.
Account importers: cPanel and Plesk
Section titled “Account importers: cPanel and Plesk”Moving a whole hosting account from cPanel or Plesk doesn’t mean re-creating everything by hand. OPanel’s importers read a standard account export and turn it into one or more sites here automatically:
| Source | What it reads |
|---|---|
| cPanel | A full-account backup (cpmove archive or backup-*.tar.gz): each domain becomes its own site, with its databases carried over and its DNS zone available for reference during cutover |
| Plesk | A Plesk backup/migration archive, imported the same way |
Start an import from Sites → Import → cPanel or Plesk, upload the export, and review the plan the importer proposes — which domains become which sites, which databases attach to which — before it runs. Large accounts with many domains are broken into one site per domain automatically, each isolated the same way any other OPanel site is.
After any import
Section titled “After any import”Whichever source you used, check the imported site works on its preview address, then point DNS at your new server — the domain page shows the records to create and confirms once they resolve, the same as for a site created directly. HTTPS certificates are issued automatically once DNS points here.