## 🗺️ Overview

If you need to move a project — including all associated tools and data such as OTTO SEO, Content Genius, Authority Building, Local SEO, Brand Vault, and Knowledge Graph — from one Search Atlas account to another, this is not something you can do yourself through the platform interface. Cross-account project migrations require action from the Search Atlas engineering team.

This article explains what to expect, how to prepare, and how to request the migration so it is completed as smoothly and quickly as possible.



## ⚠️ Important: Prepare the Destination Account First

Before submitting your migration request, you must take one critical step to avoid conflicts during the transfer:

1. **Delete any existing version of the project from the destination account.** If the same domain or project already exists in the account you are migrating into, it will cause a conflict that can block or delay the migration. Remove it first, then submit your request.

If you are unsure whether a duplicate project exists, review your project list in the destination account before proceeding.



## 📋 What Information to Have Ready

To process your migration request efficiently, the support team will need the following details. Gather these before reaching out:

- **The domain or project name** to be migrated (for example, vancouvergranite.com)
- **The source account** — the account ID or email address the project is currently in
- **The destination account** — the account ID or email address you want the project moved into
- **A list of tools and data to include** in the migration (for example: OTTO SEO, Content Genius, Authority Building, Local SEO, Brand Vault, Knowledge Graph)

## 🛠️ How the Migration Process Works

Cross-account migrations are handled entirely by the Search Atlas engineering team. Here is what happens after you submit your request:

1. A support agent receives your request and reviews the details you have provided.
2. The request is escalated to the specialized engineering team responsible for project and OTTO migrations.
3. Engineering performs the full migration, transferring the project and all associated tool data to the destination account.
4. You are notified once the migration is complete and the fix is live in your account.

Migration timelines can vary depending on the complexity of the project and the engineering team's queue. The process may take more than one business day for large or multi-tool projects.



## 💡 Tips to Avoid Common Issues

- **Delete the duplicate project first.** As noted above, any existing copy of the project in the destination account must be removed before migration begins.
- **Be specific about what needs to move.** The more clearly you list the tools and data you need migrated, the faster engineering can act.
- **Do not recreate the project manually** in the destination account after submitting your request. Wait for engineering to confirm the migration is complete before making changes.
- **Check both accounts after migration is confirmed.** Verify that all tool data — including OTTO settings, local SEO data, and content — has transferred correctly to the destination account.

## 🤝 How to Submit Your Migration Request

Because this process requires engineering involvement, there is no self-serve option in the platform at this time. To get started, contact the support team directly through the platform chat.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.

When you open the chat, include all the details listed in the *What Information to Have Ready* section above so your request can be escalated to engineering without delays.