---
title: "Guidance for Migrating BigTemplate from Data Center to Atlassian Cloud"
canonical: "https://support.appfire.com/space/SUPPORT/3754688774/Guidance%20for%20Migrating%20BigTemplate%20from%20Data%20Center%20to%20Atlassian%20Cloud"
format: markdown
---
## Problem

Customers preparing to migrate from Jira or Confluence Data Center to Atlassian Cloud may ask how to measure BigTemplate usage, identify configuration dependencies, and determine what must be retained, replaced, or retired. BigTemplate does not provide general usage statistics that can be reviewed as an adoption report.

> ℹ️ **Scope:** This guidance applies to BigTemplate for Data Center. Confirm the installed app version and the customer’s migration plan before providing migration-specific advice.

## 🌱 Solution

### 1. Confirm the customer’s environment

- Confirm the hosting platform: Jira or Confluence Data Center.
- Record the BigTemplate version and the planned Jira or Confluence version.
- Check whether BigPicture or BigGantt is installed, because BigTemplate usage may be associated with those apps.
- Ask whether the migration is planned as a single wave or multiple phases and whether BigTemplate is already installed on the target Cloud site.

### 2. Explain available usage identification

There are no general BigTemplate usage statistics or adoption reports available for this assessment. Administrators can identify usage through the BigTemplate configuration interface:

1. Open **Administration**.
2. Select **Apps**.
3. Open **BigTemplate configuration**.
4. Select **Widget**.
5. Review the Jira spaces shown as using the app.

This UI check is the supported first step for identifying spaces associated with BigTemplate.

### 3. Assess configuration dependencies

Ask the customer to inventory the following items and classify each as **Retain**, **Replace**, or **Retire**:

- Spaces or projects using BigTemplate widgets.
- Templates and user-generated content created with the app.
- BigPicture or BigGantt boxes that reference BigTemplate functionality.
- Scope definitions and other app-specific configurations.
- Business-critical reports, pages, exports, or operational processes dependent on the app.

For BigPicture-related usage, the customer should also verify **Box Configuration > Tasks > Scope definition** in the UI. Where database access is available, qualified administrators may inspect the relevant BigPicture scope data, including the `AO_0456E7_BAT_SCOPE` table. Database analysis should be treated as an investigation aid, not a substitute for UI validation.

### 4. Provide the migration documentation

Share the official migration guidance and ask the customer to complete its prerequisites before scheduling the migration:

- [Migration to Cloud with JCMA: BigTemplate migration](https://support.appfire.com/space/DLP/2056814695/Migration+to+Cloud+with+JCMA:+BigTemplate+migration)
- [BigTemplate widget](https://support.appfire.com/space/BTdc/3536224563/BigTemplate+widget)

> ⚠️ **Migration caution:** Advise the customer to review overwrite behavior when BigTemplate data already exists in Cloud. Data migrated from Data Center may overwrite corresponding Cloud data. Confirm the target state and back up relevant content before proceeding.

### 5. Set expectations about migration scope

- Confirm that the app version meets the documented JCMA requirements. The internal triage guidance identified BigTemplate **8.17.1 or later** as a prerequisite; verify this against the current migration documentation before communicating it as definitive.
- Explain that What-if scenarios are not migrated and require manual handling.
- Do not promise database queries, REST APIs, or support scripts unless they have been verified for the customer’s app version and deployment.
- Recommend a test migration or assessment validation before the production migration.

## Support handling checklist

- [ ] Confirm hosting platform, app version, product version, and migration target.
- [ ] Confirm whether BigPicture or BigGantt is installed.
- [ ] Direct the customer to the BigTemplate Widget configuration page.
- [ ] Ask the customer to inventory business-critical usage and configuration dependencies.
- [ ] Share the official BigTemplate migration documentation.
- [ ] Explain What-if scenario and overwrite considerations.
- [ ] Register the request under the customer’s Appfire migration epic when multiple app assessments are involved.
- [ ] Escalate JCMA validation errors or requests for deep database interpretation to Engineering or L3.

> ✅ **Recommended outcome:** The customer should leave the assessment with a verified list of spaces and configurations using BigTemplate, an agreed Retain/Replace/Retire decision for each dependency, and a documented migration plan validated against the current Appfire guidance.

## 📎 Related articles

- [BigTemplate widget](https://support.appfire.com/space/BTdc/3536224563/BigTemplate+widget)
- [Migration to Cloud with JCMA: BigTemplate migration](https://support.appfire.com/space/DLP/2056814695/Migration+to+Cloud+with+JCMA:+BigTemplate+migration)