---
title: "Resolving Migration Failures in BigGantt Due to Dormant Tenant Status"
canonical: "https://support.appfire.com/space/SUPPORT/3554083144/Resolving%20Migration%20Failures%20in%20BigGantt%20Due%20to%20Dormant%20Tenant%20Status"
format: markdown
---
This article explains how to resolve migration or registration failures in BigGantt when a tenant is in a dormant state.

## Summary

During the migration or registration of BigGantt on Atlassian Cloud, the process may fail if the tenant record in the system manager is flagged as dormant. This status prevents active operations and requires manual intervention to restore functionality.

## Symptoms

When you attempt to migrate or register the application, the process does not complete. Internal logs or system manager checks indicate that the tenant status is set to **Dormant**.

## Cause

The tenant record exists in the database but is marked with a status that blocks new registration or migration events. This typically occurs when a previous instance was deactivated or if there is a conflict with legacy data.

## Resolution

To resolve this issue, the engineering team must update the tenant status.

1. Contact the engineering team to request a status update for the affected tenant.
2. Provide the Jira Cloud URL and the Forge Cloud ID associated with the instance.
3. The engineering team must stash the existing dormant record or update the status to active.
4. In the *BigGantt* configuration page, retry the migration or registration process.

The migration proceeds once the dormant status is cleared.