> 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/welcome-to-duplify/key-benefits-of-duplify.md). # Key benefits of Duplify Learn the key advantages of using Duplify to export and sync your Shopify store data. Duplify is designed to make exporting and syncing Shopify store data faster and easier. It provides tools and features that help merchants manage store migrations and updates efficiently. ### Why merchants use Duplify * **Wide export options** – Export products, collections, pages, theme configuration, metafields, metaobjects, navigation, customers, orders, content files, and more. * **Auto-syncing** – Keep products and collections updated automatically across multiple destination stores. * **Flexible licensing** – A single source store license covers unlimited destination stores. * **Time-saving setup** – Streamlined interface reduces setup time and repetitive work. * **User-friendly interface** – Easy to understand and navigate, designed specifically for Shopify merchants. These features help merchants move and manage their store data with less manual work, reducing errors and saving time. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://support.duplifyapp.com/welcome-to-duplify/key-benefits-of-duplify.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.