> For the complete documentation index, see [llms.txt](https://support.duplifyapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.duplifyapp.com/try-duplify/running-a-demo.md).

# Running a demo

Learn how to run a demo export to test out Duplify.

A demo export lets you test Duplify by transferring a small number of products from your source store to a destination store. This gives you a quick preview of how your data will be copied, so you can check results and understand the process before performing a full export.

## Before you begin

Before you start the demo, make sure you've:

* [Installed Duplify](/getting-started/installing-duplify.md) on both the source and destination stores.
* [Connected your stores](/using-duplify/connecting-stores.md) so data can be transferred.

## Running a demo

1. After you've [connected your stores](/using-duplify/connecting-stores.md), click **Start demo**.
2. Duplify will export 5 products from the source store to the destination store.
3. After the demo finishes, check your destination store to see the demo products.

You can proceed to a full export when you're ready.

To avoid duplicates, we automatically remove the 5 demo products from your destination store.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.duplifyapp.com/try-duplify/running-a-demo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.