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

# Manage and duplicate Flows

> Duplicate Fliqr AI Flows for safe releases, copy a Flow to another workspace or page, and keep your Flow library maintainable.

Treat Flows like production code. Duplicate before risky edits, name clearly, and retire obsolete versions on purpose.

## Duplicate for safe changes

<Steps>
  <Step title="Copy the live Flow">
    Open the Flow → use the builder submenu / duplicate control to create a copy.
  </Step>

  <Step title="Edit the copy">
    Make breaking changes only on the copy. Keep the original published and stable.
  </Step>

  <Step title="Test and publish the copy">
    Run [Test Flow](/docs/core-concepts/flows/test-and-publish), then publish the copy.
  </Step>

  <Step title="Cut traffic over">
    Point Automation Rules, menus, drips, and buttons at the new Flow. Monitor, then archive the old one.
  </Step>
</Steps>

## Copy a Flow to another workspace or page

If you operate multiple workspaces (for example multiple Facebook Pages / channel accounts), you can copy a Flow across them:

1. Open the source Flow in the builder.
2. Open the top-right submenu.
3. Choose the destination workspace/page.
4. Confirm the copy, then publish and reattach triggers on the destination.

Channel connections and some integrations may still need configuration on the destination account.

## Naming conventions

Good names describe **outcome + channel/context**:

* `Onboarding — WhatsApp`
* `FAQ menu — Omnichannel`
* `Booking v2 — Telegram`

Avoid `Flow 3` and `Copy of Copy of …`.

## Library hygiene

| Practice                      | Why                                                                      |
| ----------------------------- | ------------------------------------------------------------------------ |
| Archive unused Flows          | Stays under the [100 Flows / account](/docs/core-concepts/flows/limits) limit |
| One owner per Flow            | Clear review path                                                        |
| Document Go to Flow contracts | Child Flows need stable field names                                      |
| Prefer modular children       | Smaller diffs, safer publishes                                           |

## Next

<CardGroup cols={2}>
  <Card title="Test and publish" icon="play" href="/docs/core-concepts/flows/test-and-publish">
    Release checklist and mid-conversation risks.
  </Card>

  <Card title="Best practices" icon="check" href="/docs/core-concepts/flows/best-practices">
    Broader Flow design standards.
  </Card>
</CardGroup>