When you move from a GoHighLevel (GHL) sub-account to a native Search Atlas account, your existing Site Explorer projects cannot be transferred. Each project must be recreated from scratch in the new account, and historical crawl and audit data stored in the GHL-managed account does not carry over.
⚙️ Why Site Explorer Projects Cannot Be Transferred
Site Explorer projects are bound to the account in which they were created. GHL sub-accounts and native Search Atlas accounts use separate account structures with no built-in migration path between them. Project settings, crawl schedules, historical audit snapshots, and trend data all remain in the source GHL account and cannot be moved to a native account.
📊 What Data Is Lost and What You Can Save
Before your GHL sub-account is closed — for example, if you are leaving an agency relationship or switching to a direct Search Atlas subscription — understand exactly what does and does not migrate.
Data that does not transfer to the native account:
- Past crawl snapshots and audit history
- Page-level issue trends and audit score history over time
- Scheduled crawl configurations and any custom crawl rules
Data you can preserve manually before migrating:
- Export each audit report as a CSV directly from the GHL sub-account (PDF export availability may vary by account type — contact support to confirm).
- Record your crawl settings — frequency, scope, and device type — so you can replicate them quickly in the new account.
🚀 How to Recreate Your Site Explorer Projects in a Native Account
Complete these steps for each domain that was active in your GHL sub-account.
- Log in to your native Search Atlas account.
- In the left sidebar, go to Site Metrics → Site Explorer (Site Explorer) and click New Project.
- Enter the domain you want to audit.
- Configure your crawl settings: crawl frequency (daily, weekly, or monthly), crawl scope (number of pages or sections to include), and device type (desktop or mobile). If you are setting up the project in a GHL context, note that the Worldwide location option is not available — select a specific country or region instead.
- Click Recrawl Site to run the first audit under the new account.
- Repeat for every additional domain previously managed under the GHL sub-account, adding them sequentially rather than all at once.
The first crawl typically completes in 5–30 minutes depending on site size. Once it finishes, your native account has a clean baseline from which you can track all future improvements.
🚧 How to Fix a Quota Exhausted Error
If you receive a Quota Exhausted error when adding projects — even when slots appear available — contact Search Atlas support. An agent can review and reset your on-page audit quota. Add projects sequentially and allow each crawl to complete before starting the next.
⚠️ Export Everything Before Your GHL Access Ends
Your GHL sub-account remains active until your agency formally closes or transfers it. Export all audit reports and note all crawl configurations before that access ends — audit history cannot be retrieved after the account is closed or revoked.
Tip: Before your agency closes or transfers your GHL sub-account, request at least 30 days of continued read access so you can complete all exports. Contact Search Atlas support if you need guidance on timing.
💡 What Starting with a Fresh Baseline Means for Reporting
Your native account begins with no historical trend data from the GHL period. This is expected. The first crawl immediately surfaces all current site issues, so you can start measuring and tracking improvements from day one. If you need a documented record of past performance, your exported CSV (or PDF, if available) reports from the GHL account serve as your historical reference.
🎯 With your projects recreated in your native Search Atlas account, you have full ownership of your crawl data and audit history going forward. If you have questions about your account transition or need help configuring Site Explorer for the first time, contact Search Atlas support or reach out to your account manager.