---
title: "How to split snapshots for large instances"
canonical: "https://support.appfire.com/space/SUPPORT/993787917/How%20to%20split%20snapshots%20for%20large%20instances"
format: markdown
---
This article explains how to create snapshots for large Jira instances by splitting them into smaller chunks. The large instance here refers to projects with more than 100,000 issues and/or a total attachment size of roughly 100 MB.

## \uD83D\uDCD8 Instructions

<u>**Method A**</u><u>** - Multiple batches of snapshots**</u>

- Filter the issues by issue type or other JQL query when creating a snapshot.
- [Learn more](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198279862) about filtering issues during a snapshot creation.

<u>**Method B**</u><u>** - Exclude attachments **</u>

- This common practice will make the snapshot file smaller and more manageable.
- More details can be found here → [https://appfire.atlassian.net/wiki/spaces/CMJ/pages/197825295](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/197825295)

<u>**Method C - Incremental Deployment**</u>

- Deploy the project configuration first and then move the data in chunks of issues.
- [Learn more](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/198116612) about the incremental deployment approach.

> ℹ️ In addition to the suggested methods, it is also advisable to increase the Java heap for your Jira to achieve the best performance and avoid potential **OutOfMemory** errors for large snapshot deployments. 
> ℹ️ 
> ℹ️ You can reference the Jira sizing guide and double the heap numbers for large deployments. A rough guideline is 12-16GB for moving a project with 100,000 issues (attachment files moved separately).
> ℹ️ 
> ℹ️ - [Jira Sizing Guide | Atlassian Support | Atlassian Documentation](https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html)

## \uD83D\uDCCB Related articles



> Macro (contentbylabel)