π¦ What this article covers
Use this guide when a project, such as a client site created for Maya, was added to the wrong account and you need to move it without losing data or history. It also explains the account structure, plan, and seats an agency needs to manage several client accounts.
β Before you move anything
Do not delete the project, disconnect the site, or rebuild it from scratch. Deleting a project permanently removes it from the account, and the product says this cannot be undone. It does not guarantee that every report, history record, and setting is deleted. Keep both accounts active until the move is confirmed.
- Identify the source account where the project was created by mistake.
- Identify the destination account that should own the project going forward.
- Confirm you can sign in to both accounts, or that the account owners can approve the move.
- Write down the project name, domain, and account emails so support can match the correct records.
- Pause new setup work on the mistaken project so history stays consistent during the transfer.
π’ Recommended order to move a project
Follow these steps in order. Moving ownership first, then checking data, prevents duplicate projects and lost history.
- Stop using the wrong account for new work. Leave the existing project in place.
- Decide the correct owner. For one client, the destination is usually that client account. For agency-managed work, the destination is the agency workspace that should hold the client.
- Check for a duplicate. If the same domain already exists in the destination, do not create another copy. Ask support to review it. They can move projects that do not already exist there, but they cannot merge the original into the existing destination project while keeping one combined history.
- Contact support and ask them to move the project. Include both account emails, the project name, the domain, and which account should be the final owner. Say clearly that the project and its connected data should be kept. Support handles the move internally. It is not a form you submit in live chat, and the original accountβs billing is not moved.
- Wait for confirmation before changing access. Do not remove users, cancel a plan, or delete the source until support confirms the move is complete.
- Review the destination project. Confirm the domain is correct and the services have reconnected. Historical reports, keywords, pages, and settings are not guaranteed to appear exactly as they did before the move, because the move reconnects the project under the new account rather than copying its stored history.
- Update seats and permissions. Give each teammate access only to the client accounts they manage.
- Archive access to the wrong account only after the destination project is verified.
π’ Agency structure for several accounts
An agency should separate ownership from day-to-day access. One agency workspace manages many client accounts. Each client project stays attached to the correct client so reporting and history remain intact.
- Agency owner: controls billing, plans, and who can be invited.
- Client accounts are separate customer accounts under the agency, shown as Agency Customers. Each client account contains that clientβs projects. They are not folders inside the agency account.
- Projects: one project per domain or site, not one project shared across unrelated clients.
- Users: people invited with a role, rather than sharing one login.
π³ Plan and seats you need
Choose a plan that covers the number of projects and client accounts you actively manage. Seats are for people, not for websites. A seat lets a teammate sign in with their own email and work on the accounts you assign.
- Projects: count each active client domain you want to track.
- Seats: count each employee, contractor, or client user who needs their own login.
- Roles: give owners and managers broader access, and limit specialists to assigned clients.
- Growth: add seats when new people join. Add project capacity when new clients are onboarded. Do not create extra personal accounts to work around limits.
If a project was created under a personal login instead of the agency, move that project into the agency structure rather than copying it. Sharing passwords is not recommended because it makes history and permissions harder to manage.
β οΈ How to avoid lost data
- Never delete a project until the moved copy is confirmed and checked.
- Do not recreate the same domain in a second account while a transfer is in progress.
- Keep billing active on the source account until the move is finished.
- Export a backup of critical reports first if you need an offline copy for your records.
π¬ Get help with a transfer
Project moves between accounts are completed by support so ownership, data, and history stay aligned. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.