Migration View in Sparkforge: Agency vs Sub-Account
Agencies see all three WordPress migration paths (plugin, manual upload, white-glove) while sub-accounts only see the two self-serve options. The agency-only white-glove option stays hidden from clients to preserve the white-label experience.
Sparkforge shows different WordPress migration options depending on whether you are signed in as the agency or as a sub-account. Agencies see the full toolbox, including white-glove assistance. Sub-accounts only see the self-serve paths.
What agencies see
Inside the WordPress Hosting dashboard, an agency owner sees three migration options:
- Effortless plugin migration — one-click migration with the Sparkforge plugin.
- Manual migration — upload an All-in-One
.wpressexport. - White-glove migration — submit a request and our WordPress specialists run the migration.
The white-glove path is exclusive to agency-level users and is invisible to clients.
What sub-accounts see
Sub-accounts only see the two self-serve options: the plugin migration and the manual .wpress upload. They never see the white-glove option, and Sparkforge does not surface any indicator that a hidden option exists.
Why the views differ
The white-glove benefit is part of the agency tier. Hiding it from sub-accounts keeps the experience consistent for clients and protects your white-label brand.
Guiding a sub-account through migration
You have two clean options when a client needs migration help:
- Point them at the plugin migration and let them run it themselves.
- Submit the white-glove request on their behalf and run the migration without them seeing the agency-only step.
Frequently Asked Questions
Can sub-accounts see the white-glove migration option?
Will my clients know the white-glove option exists?
Can I run a white-glove migration on behalf of a sub-account?
Why are the migration paths different for agencies and sub-accounts?
Was this article helpful?
Thanks for the feedback.