{"id":6363,"date":"2026-10-01T10:24:35","date_gmt":"2026-10-01T07:24:35","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6363"},"modified":"2026-10-01T10:24:36","modified_gmt":"2026-10-01T07:24:36","slug":"migrate-reseller-business-spanel","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/migrate-reseller-business-spanel\/","title":{"rendered":"Migrating Your Reseller Business to SPanel Without Your Clients Noticing"},"content":{"rendered":"\n

Did you know that <\/strong>you can move your reseller clients to an SPanel-powered managed VPS with ScalaHosting<\/strong><\/a> without changing anything they see? Their websites keep the same domains, their email keeps working, while the control panel login still carries your company name and logo. SPanel’s server-wide branding is included for free on every plan, so the surface your clients recognize remains identical as you swap the underlying infrastructure.<\/p>\n\n\n\n

The migration every reseller is afraid of<\/strong><\/h2>\n\n\n\n

Imagine that:<\/p>\n\n\n\n

Priya runs a small hosting business out of Bristol – 38 client websites, mostly local trades and a couple of online shops. Her current panel is showing its age, and the per-account costs keep climbing, so she wants to move everyone to SPanel on a ScalaHosting managed VPS. <\/p>\n\n\n\n

One thing stops her cold, though – the fear that a client logs in one morning, sees a different name on the screen, Googles it, and starts asking who really runs their hosting service. For a reseller, that question should never come up.<\/p>\n\n\n\n

What does an “invisible migration” actually mean?<\/strong><\/h2>\n\n\n\n

An invisible migration is one where every surface your clients can see – their domain, your brand, their login, their email – stays exactly the same, while the panel and server underneath are replaced.<\/p>\n\n\n\n

That works because what a client recognizes is what you<\/em> control, not what’s tied to the old panel. Clients identify their hosting by three signals: the domain<\/strong> their site runs on, the name and logo<\/strong> on the login page, and the email addresses<\/strong> they send from. None of those belong to the software you are leaving. The domain is theirs. The brand is yours. The email follows the domain.<\/p>\n\n\n\n

The three surfaces your clients see<\/strong><\/h2>\n\n\n\n

Their own domain stays their own domain.<\/strong> A client whose shop is at Bristol-Bikes.com, for example, keeps that address through the move. You copy the site to the new server, test it, then point the DNS over when you are ready.<\/p>\n\n\n\n

Your brand stays on the login page.<\/strong> This is where most control panel moves leak: the login screen carries the vendor’s name, or the login button drops the client onto the upstream provider’s domain. With SPanel branding on, the login page shows your company name and logo, served from the client’s own domain at the neutral \/hostpanel path – and that branded login is the default behavior, not an assembly project<\/a>.<\/p>\n\n\n\n

Their email keeps flowing.<\/strong> Mailboxes move with the account, and because the domain is unchanged, addresses remain the same as well. With DNS planned properly, mail keeps delivering across the cutover.<\/p>\n\n\n\n

To summarize: A migration your clients never notice is the best kind – same domain, same brand, same login, only the engine underneath has changed.<\/p>\n\n\n\n

How SPanel keeps your name on the door<\/strong><\/h2>\n\n\n\n

Branding in SPanel entails numerous options on a single screen, applied across the whole server. <\/p>\n\n\n\n

On the Branding<\/strong> screen in the Admin Interface<\/strong> (Server Management \u2192 Branding), you set your brand name, upload your logo, and switch the login URL from the default \/spanel to the branded \/hostpanel. Every hosted domain then serves a login page under your name, and every new account inherits it automatically – you never re-apply it per client. That matters during a migration, when you are creating dozens of accounts in a short window and want all of them branded from birth. <\/p>\n\n\n\n

That same Branding screen is the heart of the five-minute white-label walkthrough<\/a>.<\/p>\n\n\n\n

This is included free on every ScalaHosting managed cloud VPS. In the wider control panel category, white-labeling has traditionally been available in a paid tier or charged per account. In comparison, SPanel treats it as part of the panel, with no surcharge.<\/p>\n\n\n\n

Weighing a reseller migration?<\/strong> ScalaHosting’s managed VPS plans include SPanel and its server-wide branding at no extra cost, plus free website migration on every plan. Brand a server and test client sites before any DNS changes.<\/p>\n\n\n\n

What stays, what changes<\/strong><\/h3>\n\n\n\n
Client-facing surface<\/strong><\/td>Changes during migration?<\/strong><\/td>Who controls it<\/strong><\/td><\/tr>
Their website’s domain<\/td>No<\/td>You \/ the client’s DNS<\/td><\/tr>
Brand on the login page<\/td>No – stays yours<\/td>SPanel Branding screen<\/td><\/tr>
Login URL<\/td>No – their own domain + \/hostpanel<\/td>SPanel<\/td><\/tr>
Their email addresses<\/td>No<\/td>The domain (unchanged)<\/td><\/tr>
The panel software underneath<\/td>Yes<\/td>You (invisible to the client)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The only row that changes is the one your clients never look at.<\/p>\n\n\n\n

Demo flow: brand the server before the first client lands<\/strong><\/h2>\n\n\n\n

The exact SPanel steps to brand the new server before you move anyone:<\/p>\n\n\n\n

    \n
  1. Log in to the Admin Interface<\/strong> of your SPanel server with your admin account.<\/li>\n\n\n\n
  2. Open Server Management \u2192 Branding<\/strong> in the Admin Interface.<\/li>\n\n\n\n
  3. In the Enter Your Brand<\/strong> field, type your company name (example here is Northwind Hosting); upload your logo under Custom logo<\/strong>; review the form before saving. The Login URL<\/strong> stays on the default \/spanel here.<\/li>\n<\/ol>\n\n\n\n
    \"Migrating<\/figure>\n\n\n\n
      \n
    1. Switch the Login URL<\/strong> option to \/hostpanel and click Save Changes<\/strong>. SPanel applies the change server-wide, and the branded login goes live within a few seconds.<\/li>\n<\/ol>\n\n\n\n
      \"Migrating<\/figure>\n\n\n\n
        \n
      1. In a browser, visit a hosted domain at the branded path – for example northwind-client.example\/hostpanel\/login – to confirm the login shows your name and logo, not the default \/spanel page.<\/li>\n<\/ol>\n\n\n\n
        \"Migrating<\/figure>\n\n\n\n

        A timeline your clients never feel<\/strong><\/h2>\n\n\n\n

        A week before.<\/strong> Lower the DNS TTL on the domains you are migrating so the final cutover propagates fast. Provision the new ScalaHosting managed VPS, brand it once with the steps above, and set up your packages.<\/p>\n\n\n\n

        Migration window.<\/strong> Copy sites, databases, and mailboxes over. Recreate each client as an SPanel account – branded automatically – and test each site before touching public DNS. ScalaHosting includes free website migration on every plan, worth using for the heavy lifting.<\/p>\n\n\n\n

        Cutover.<\/strong> Point each domain’s DNS at the new server. Because the TTL is already low, visitors and mail follow within minutes, not days. The client’s address bar never changes; only the server answering it does.<\/p>\n\n\n\n

        After.<\/strong> Raise TTLs back to normal and decommission the old accounts once everything is confirmed on SPanel.<\/p>\n\n\n\n

        Finishing the white-label job so nothing leaks later<\/strong><\/h2>\n\n\n\n

        Branding the panel covers the screen clients look at most, but a complete reseller setup includes two more pieces that are best handled during the migration. <\/p>\n\n\n\n

        Set a server hostname on your own domain – something like server1.northwind.example – so mail and FTP client settings carry your name. Run branded nameservers (ns1\/ns2 on your domain) so client DNS delegation points at you. SPanel supports all three, and together they leave no visible trace of who runs the metal underneath; the full sequence lives in the complete white-label checklist<\/a>.<\/p>\n\n\n\n

        Be honest about the edges, too. <\/p>\n\n\n\n

        Third-party tools inside the panel – the webmail client’s own interface, application installers, phpMyAdmin – keep their own product names, as on every hosting panel. The branded surfaces are the panel identity, the login page, the login URL, and the webmail entry. Done across all three pieces, that invisibility is also why clients stay – the argument behind white-labeling as a retention feature.<\/p>\n\n\n\n

        Where SPanel fits<\/strong><\/h2>\n\n\n\n

        SPanel is ScalaHosting’s control panel, included free on every ScalaHosting managed VPS. Scala runs this solution across more than 700,000 websites in over 120 countries. The white-label setup resellers usually pay extra for elsewhere is the default here, with no per-account math. <\/p>\n\n\n\n

        Have the need of a new feature?<\/p>\n\n\n\n

        Branding requests are shaped openly through the Cloud Democracy Project<\/a>. You can suggest a new functionality, and the most popular ones are quickly added to new SPanel versions. <\/p>\n\n\n\n

        You can also learn more about our free website migration<\/a> to understand just how easy it is to switch your business to ScalaHosting.<\/p>\n\n\n\n

        FAQ<\/strong><\/h2>\n\n\n\n

        Q:<\/strong> Will my clients have to log in somewhere new after I migrate?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> No. With SPanel branding enabled, each client logs in at their own domain plus the \/hostpanel path – the same address they already use, carrying your name and logo.<\/p>\n\n\n\n

        Q:<\/strong> Will my clients see the SPanel name during or after the move?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> The panel identity, login page, login URL, and webmail entry carry your brand. Embedded third-party tools keep their own names, as on any panel. Set a branded hostname and nameservers, and there is no vendor surface left to find.<\/p>\n\n\n\n

        Q:<\/strong> Does moving to SPanel mean downtime my clients will notice?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> Not if you plan DNS properly. Lower the TTL ahead of time, copy and test on the new server, then cut over. Visitors and mail follow within minutes.<\/p>\n\n\n\n

        Q:<\/strong> Do my clients need to change their domain or DNS settings?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> No. You manage the cutover; the client keeps the same domain and does nothing.<\/p>\n\n\n\n

        Q:<\/strong> Is migration to ScalaHosting actually free?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> Yes. ScalaHosting includes free website migration on every plan, regardless of platform, size, or number of sites, with no downtime. Keep it distinct from the separate performance guarantee, which has its own conditions.<\/p>\n\n\n\n

        Q:<\/strong> Can I keep my own brand on the panel after I move?<\/strong> <\/p>\n\n\n\n

        A:<\/strong> Yes – that is the point. Branding is server-wide: one setting puts your name and logo on every hosted domain’s login page, existing and future accounts alike, so you never rebrand client by client.<\/p>\n\n\n\n