> ## Documentation Index
> Fetch the complete documentation index at: https://developers.scrunch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch from Another AI Visibility Tool in One Conversation

> MCP workflow to migrate brands, personas, tags, competitors, and your full prompt library from another AI visibility tool into Scrunch in one chat.

Switching from another AI visibility tool? You don't have to rebuild your setup by hand. Run one prompt in your current tool to export everything — brands, personas, tags, alternative names, competitors, and your full prompt library — then paste the result into a Scrunch MCP chat and have your AI agent recreate it all directly.

<Info>
  **Tools used in this workflow**

  | Tool                                                | Required? | Notes                                                                                                                              |
  | --------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------- |
  | Scrunch MCP                                         | Required  | Editor or Admin-level permissions on a Scrunch Agency or Enterprise plan required                                                  |
  | Your current tool's MCP, CSV export, or settings UI | Required  | Any source where your existing configuration is visible — MCP-connected chat, downloaded CSVs, or text copied from a settings page |

  Step 2 uses write operations in Scrunch. Your AI agent will confirm before creating anything — you'll see each step as it runs.
</Info>

***

## Step 1 — Export your setup

Pick the path that matches the tool you're moving off of.

<Tabs>
  <Tab title="Tool with MCP or API-connected chat">
    Open a chat with the AI assistant that's connected to your current tool's MCP server (or its API), and paste this prompt. It returns a structured, copy-paste-ready dump of your entire configuration.

    ```text theme={null}
    Export everything you can read about my AI visibility configuration from the tool you're connected to. Preserve my exact wording where possible — especially for prompt text, brand descriptions, alternative names, and persona definitions.

    ## Categories (output in this order):

    1. **Brands** — One entry per tracked brand. For each, include: name, primary website/domain, one or two sentence description, alternative names / aliases / variants, and any unique identifier the tool stores.

    2. **Personas** — Audience personas defined for each brand. Verbatim names and descriptions. Note which brand each persona belongs to.

    3. **Tags / Topics** — Every tag or topic label used to categorize prompts. Include the label and a one-line meaning if available. Note whether tags are global or scoped to a specific brand.

    4. **Competitors** — One entry per competitor, grouped under the brand it's tracked for. Include competitor name and website/domain.

    5. **Prompts** — One entry per tracked prompt. For each, include: the brand it belongs to, the prompt text verbatim, any persona it's assigned to, and any tags applied.

    ## Format:

    Use a section header for each category. Within each category, list one entry per line. Format brand and prompt lines so they're machine-readable:

    - Brand: `<Brand Name> | website: <domain> | aliases: <comma-separated> | description: <text>`
    - Persona: `<Brand Name> | persona: <name> | description: <text>`
    - Tag: `<tag label> | meaning: <text> | scope: <brand name or "global">`
    - Competitor: `<Brand Name> | competitor: <name> | website: <domain>`
    - Prompt: `<Brand Name> | persona: <name or "none"> | tags: <comma-separated or "none"> | prompt: <verbatim prompt text>`

    Preserve original wording. Do not paraphrase prompt text, descriptions, or persona definitions.

    ## Output:

    - Wrap the entire export in a single fenced code block for easy copying.
    - After the code block, state whether this is the complete set or whether any category was truncated. If truncated, say which category and roughly how many entries remain.
    ```

    Save the resulting code block — you'll paste it into Scrunch in Step 2.
  </Tab>

  <Tab title="Tool with CSV export only">
    Download every CSV your current tool offers — usually one for brands, one for prompts, one for competitors, and sometimes a tags or personas export. Then open a fresh chat with any capable AI assistant (Claude, ChatGPT, etc.), paste **all** the CSV contents in one after another, and use this prompt to reformat them.

    ```text theme={null}
    I've pasted CSV exports from my AI visibility tool below. Reformat them into a single, structured export I can hand to another tool's AI agent.

    Preserve my exact wording where possible — especially for prompt text, brand descriptions, alternative names, and persona definitions.

    ## Categories (output in this order):

    1. **Brands** — One entry per brand: name, primary website/domain, description, alternative names / aliases, identifier.
    2. **Personas** — Audience personas per brand, verbatim names and descriptions.
    3. **Tags / Topics** — Every tag or topic label, with a one-line meaning if present in the CSVs.
    4. **Competitors** — One entry per competitor, grouped under its brand.
    5. **Prompts** — One entry per prompt, with brand, persona (if any), tags (if any), and the prompt text verbatim.

    ## Format:

    Section header per category, one entry per line. Use these line shapes:

    - Brand: `<Brand Name> | website: <domain> | aliases: <comma-separated> | description: <text>`
    - Persona: `<Brand Name> | persona: <name> | description: <text>`
    - Tag: `<tag label> | meaning: <text> | scope: <brand name or "global">`
    - Competitor: `<Brand Name> | competitor: <name> | website: <domain>`
    - Prompt: `<Brand Name> | persona: <name or "none"> | tags: <comma-separated or "none"> | prompt: <verbatim prompt text>`

    Do not paraphrase prompt text, descriptions, or persona definitions.

    ## Output:

    - Wrap the entire export in a single fenced code block.
    - After the code block, note any fields that were missing from the CSVs (e.g., "no personas column was present").

    --- CSV content begins below ---

    [paste all CSV contents here]
    ```
  </Tab>

  <Tab title="Paste raw text from anywhere">
    If your current tool has no MCP, no API, and no CSV export, copy whatever text you can pull from the settings or configuration screens — brand names, prompt lists, persona blurbs, competitor lists, tag labels. Paste it all into a fresh chat with any capable AI assistant and use this prompt to normalize it.

    ```text theme={null}
    I've pasted raw text copied from the settings of my AI visibility tool below. The structure is inconsistent — some sections are tables, some are lists, some are paragraphs. Normalize it into a single, structured export.

    Preserve my exact wording where possible — especially for prompt text, brand descriptions, alternative names, and persona definitions.

    ## Categories (output in this order):

    1. **Brands** — name, primary website/domain, description, alternative names / aliases.
    2. **Personas** — per brand, verbatim names and descriptions.
    3. **Tags / Topics** — every tag label, with a one-line meaning if present.
    4. **Competitors** — per brand, name and website.
    5. **Prompts** — per brand, with persona (if any), tags (if any), and verbatim prompt text.

    ## Format:

    Section header per category, one entry per line:

    - Brand: `<Brand Name> | website: <domain> | aliases: <comma-separated> | description: <text>`
    - Persona: `<Brand Name> | persona: <name> | description: <text>`
    - Tag: `<tag label> | meaning: <text> | scope: <brand name or "global">`
    - Competitor: `<Brand Name> | competitor: <name> | website: <domain>`
    - Prompt: `<Brand Name> | persona: <name or "none"> | tags: <comma-separated or "none"> | prompt: <verbatim prompt text>`

    If a field isn't present in the source text, write `unknown` rather than guessing. Do not paraphrase prompt text or descriptions.

    ## Output:

    - Wrap the entire export in a single fenced code block.
    - After the code block, list anything you couldn't confidently place into a category.

    --- pasted text begins below ---

    [paste raw text here]
    ```
  </Tab>
</Tabs>

***

## Step 2 — Import into Scrunch

Open a fresh chat with an AI assistant connected to the Scrunch MCP. Paste the export from Step 1, then paste this prompt directly after it.

```text theme={null}
The block above is an export of my AI visibility setup from another tool. Recreate it in Scrunch. Confirm with me after each step before moving on.

Step 1 — Parse and confirm:
Read the export and tell me:
- How many brands you found
- How many personas, tags, competitors, and prompts you found
- Anything that looks ambiguous, duplicated, or incomplete

Wait for me to confirm before writing anything.

Step 2 — Create the brands:
Create each brand in Scrunch with its name, website, description, and alternative names from the export. After all brands are created, list them back with their new Scrunch brand IDs.

Step 3 — Configure personas and tags:
For each brand, set up the personas listed in the export. Then create the tags from the export — global tags first, then brand-scoped tags. Confirm when done.

Step 4 — Add competitors:
For each brand, add the competitors listed in the export with their websites. Confirm the full competitor count per brand when done.

Step 5 — Create the prompt library:
For each brand, create every prompt from the export. Apply the persona and tags exactly as listed. Use the prompt text verbatim — do not rewrite or paraphrase. Confirm the prompt count per brand when done.

Step 6 — Final summary:
List everything you created: brands (with IDs), personas per brand, tags, competitors per brand, and prompts per brand grouped by tag. Flag anything you skipped or couldn't import and explain why.
```

**What you get:** A Scrunch organization that mirrors your previous setup — same brands, same personas, same tags, same competitors, same prompts. First metrics begin landing within 24–48 hours as the prompt library starts running. After 30 days you'll have enough data to compare against your old tool side by side.

***

## Tips

<AccordionGroup>
  <Accordion title="If your export got truncated">
    MCP tool results are typically capped, and very large prompt libraries can spill past the limit. Re-run the Step 1 prompt once per category — "export only brands and personas", then "export only prompts for brand X" — and import the chunks in sequence. Scrunch's import prompt is happy to pick up where it left off if you tell it which brands are already created.
  </Accordion>

  <Accordion title="If your previous tool used different tag names">
    Tag conventions differ across tools. Before Step 5, tell the Scrunch agent how to normalize: e.g., "Map any tag that means top-of-funnel to 'awareness', any comparison tag to 'consideration', and any purchase-intent tag to 'decision'." The agent will apply the mapping consistently across every prompt.
  </Accordion>

  <Accordion title="Migrating multiple workspaces or clients">
    Run Step 1 once per workspace in your old tool. Keep each export separate. Then run Step 2 once per export in its own Scrunch chat so the agent doesn't cross-wire competitors or tags between unrelated brands.
  </Accordion>

  <Accordion title="Verifying nothing got missed">
    After Step 6, ask Scrunch: "List every prompt grouped by brand and tag, with persona where assigned." Diff that against your Step 1 export. Anything missing is usually a tag mapping the agent skipped — point it out and ask the agent to backfill.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="New Brand Live in One Conversation" icon="rocket" href="/mcp/workflows/new-brand-live">
    Setting up an additional brand from scratch after the migration is done.
  </Card>

  <Card title="Find Visibility Gaps Worth Fixing" icon="magnifying-glass" href="/mcp/workflows/find-visibility-gaps">
    Once 30 days of data are in, find where your migrated setup is winning and where it's not.
  </Card>
</CardGroup>