> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/maps/duplicate-and-move-maps.md). # Duplicate and move maps Duplicate a Felt map as a template or backup. Move maps into projects and folders, or copy them to another workspace. To copy a map, open the **Felt** menu and click **File** > **Duplicate map**. The copy has its own link, but in the same workspace its Felt Server layers stay synced with the original. Moving a map keeps its link and puts it in your **Drafts**, a project, or a folder in the same workspace. ## Duplicate a map To duplicate a Felt map, you need a seat in the workspace where you want to put the copy. Duplicating works on every plan, including Free. If you have View or Contribute access to the map, or you're logged in and viewing a public map, the map's **Duplicate map and data** setting must be on, which it is by default. See [Map settings](/maps/map-settings.md#viewer-permissions). 1. Open the map. 2. Open the **Felt** menu and click **File** > **Duplicate map**. Felt opens the copy. If you don't have a seat in the map's workspace, click **Duplicate map to** and select a paid workspace where you have a seat. If neither option appears in the **File** menu, you aren't logged in, the setting is off, or you don't have a seat in any workspace. ### What a copy includes You own the duplicated map. It has the original's name followed by "(copy)". * Copied: layers, annotations, styles, the legend, dashboard components, extensions, print layouts, and custom icons. * Not copied: comments and the original map's sharing settings. Share the copy separately. See [Share a map](/share/share-a-map.md). * Location: the original's project and folder if you have Edit access to that project; otherwise, your **Drafts**. A copy in the same workspace keeps Felt Server layers synced with the original, so data edits on either map appear on both. See [How copies stay in step](/layers/copy-and-duplicate-layers.md#how-copies-stay-in-step). ### Use a map as a template To use a map as a template, set it up with the layers, styles, and legend you want to reuse. Put it in a project your team can see, and have each person duplicate it. Felt has no separate template feature. ## Move a map within a workspace Moving a Felt map keeps existing links and embeds working. Everyone with access to its new project can see it. You need Edit access to the project the map is in and to the project you move it to, unless the map is in your **Drafts**. 1. Open the map and click **Edit map** in the toolbar at the top right of the map. 2. Open the **Felt** menu and click **File** > **Move map…**. You can also click the project name next to the map's title. 3. In the **Move map** dialog, select a project, a folder, or **Drafts**. 4. Click **Move**. ## Copy a map to another workspace Felt can't move maps between workspaces, but you can copy a map into another workspace. For copies between workspaces, you can only duplicate maps into paid workspaces. To copy from the **Move map** dialog, you need Edit access to the map's project, or the map must be in your **Drafts**. You also need Edit or Admin access to the other workspace, or Edit access to a project in it. Otherwise, use **Duplicate map to**. See [Duplicate a map](#duplicate-a-map). 1. Open the map. 2. Open the **Felt** menu and click **File** > **Move map…**. 3. In the **Move map** dialog, select the other workspace from the list at the bottom left. Felt shows *Maps can only be duplicated across workspaces. The original will remain.* 4. Select a project or folder in that workspace. 5. Click **Duplicate**. A copy in another workspace gets its own independent layers, which don't sync with the original, and a new link. If the original is embedded on a website, update the embed code to show the copy. See [Embed a map](/share/embed-a-map.md). The original stays until you [delete it](/maps/organize-maps.md#delete-a-map). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.felt.com/maps/duplicate-and-move-maps.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 `automate deployments from our CI pipeline` 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.