/
Migration to Jira Cloud

Migration to Jira Cloud

Overview

This guide walks you through migrating STAGIL Tables for Jira from Data Center (DC) to Cloud. While the core functionality remains consistent, there are some architectural differences between the two platforms that you should be aware of before migrating.

In the Cloud version, tables are rendered as panels rather than native Jira custom fields. This is due to various Atlassian Cloud platform limitations, including size restrictions on custom fields, JQL autosuggestions, and more.

There are also some differences in JQL search behavior, REST API authentication, and permission configuration between the platforms. For a detailed comparison of all features, see the Feature parity: Cloud vs DC (Data Center)

Prerequisites

Before starting your migration, ensure the following:

  • Latest version of STAGIL Tables for Jira is installed on both your DC instance and Cloud site

  • Atlassian Jira Cloud Migration Assistant is installed and configured in your DC instance

  • You have admin permissions on both DC and Cloud instances

  • All users referenced in your tables exist in the Cloud instance

  • Review the feature parity document to understand any differences that may affect your workflows

Migration Process

Step 1: Prepare Your DC Instance

  1. Ensure your STAGIL Tables for Jira DC app is up to date

  2. Document your current table configurations and permissions

  3. Note any tables using features that may differ in Cloud (refer to the feature parity document)

Step 2: Run the Migration

  1. Open the Jira Cloud Migration Assistant in your DC instance

  2. Follow the standard Atlassian migration workflow

  3. STAGIL Tables data will be included automatically as part of the migration process

Step 3: Restore Large Tables (Optional)

Tables exceeding 32KB are migrated but truncated. Most users won't be affected by this — 32KB is quite substantial. To give you an idea: a table would typically need around 300–400 rows with 10 columns of moderate text content, or 100+ rows with 15 columns containing longer text values to reach this limit.

If you have tables that were truncated during migration, use the workaround below to restore the full data.

  1. In your DC instance, identify tables exceeding 32KB and use Bulk Export to export their data to CSV

  2. In your Cloud instance, use Bulk Import to import the CSV data

Step 4: Verify Your Data

After migration completes:

  1. Spot-check tables across different projects to confirm data integrity

  2. Verify table configurations and column types

  3. Review permissions and ensure they transferred correctly

  4. Test table functionality in issue views, create screens, and transition screens

Problem Reporting and Support

If you encounter any issues during or after migration, first check the feature parity document to confirm the behavior isn't an expected difference between platforms. If you need further assistance, contact us at https://timetoactgroup.atlassian.net/helpcenter/stagil/portal/1228/group/1296 with the following information:

  • Description of the issue

  • Screenshots or error messages

  • Affected project and table details

  • Steps to reproduce

  • Jira DC version

  • STAGIL Tables for Jira DC version

We're here to help make your migration as smooth as possible!