---
title: "How to Manage Worklogs and BigPicture Migration Guardrails"
canonical: "https://support.appfire.com/space/SUPPORT/3523903827/How%20to%20Manage%20Worklogs%20and%20BigPicture%20Migration%20Guardrails"
format: markdown
---
This article covers how to handle worklog migration challenges when moving from Jira Data Center to Cloud, specifically to satisfy migration guardrails and ensure a smooth BigPicture app transition.
## Summary
This guide addresses two primary scenarios encountered during a Jira Cloud migration involving BigPicture:
1. **Moving worklogs between issues** to comply with migration guardrails (e.g., issue size limits).
2. **Verifying BigPicture migration** after using the Jira Cloud Migration Assistant (JCMA).
---
## Scenario 1: Moving Worklogs Between Issues (Guardrail Compliance)
### Problem/Context
During migration, you may encounter "guardrails" or limitations regarding the number of worklogs on a single Jira issue. To proceed, it may be necessary to redistribute worklogs from one Data Center ticket to another before initiating the migration.
### Solution
Jira does not provide a native UI feature to move worklogs between issues. This must be performed using a custom script or the Jira REST API.
#### Workaround: ScriptRunner for Jira (Data Center)
You can use a ScriptRunner script to programmatically move worklogs. The following logic outlines the approach:
1. Identify the source issue and the target issue.
2. Retrieve all worklog entries from the source issue.
3. Create new worklog entries on the target issue using the data from the source (author, time spent, date, comment).
4. Delete the worklogs from the source issue to avoid duplication.
**Note:** Ensure you test this in a staging environment first, as deleting worklogs is irreversible.
---
## Scenario 2: BigPicture Migration and Post-Migration Verification
### Problem/Context
When migrating BigPicture from Data Center to Cloud (including BigPicture Enterprise), it is critical to ensure that all app-related data and worklogs are correctly transferred.
### Solution
Use the **Jira Cloud Migration Assistant (JCMA)** for the migration process. Follow these steps to ensure success:
#### 1. Pre-Migration Preparation
- Review the official [BigPicture Migration Documentation](https://support.appfire.com/space/DLP/297896980/Migration+using+Jira+Cloud+Migration+Assistant+(JCMA)).
- Perform at least one test migration to a sandbox environment to identify potential issues.
#### 2. Migration Execution
- Run the migration using JCMA.
- Monitor the progress specifically for worklog migration, as high volumes of worklogs can sometimes lead to timeouts or missing entries.
#### 3. Post-Migration Checks
After JCMA completes, perform the following verifications:
- **Worklog Integrity:** Compare the worklog counts on key issues between the source DC instance and the target Cloud instance.
- **App Configuration:** Verify that BigPicture programs, boxes, and Gantt charts reflect the source data.
- **Documentation Reference:** Consult the [Post-Migration Checklist](https://support.appfire.com/space/DLP/2056683595/Migration+to+Cloud+with+JCMA:+After+migration) for detailed verification steps.
---
## Related Resources
- [Migration to Cloud with JCMA: Migration Process](https://support.appfire.com/space/DLP/2056650844/Migration+to+Cloud+with+JCMA:+Migration+process)
- [https://confluence.atlassian.com/cloud/jira-cloud-migration-assistant-guardrails-1026050480.html](https://confluence.atlassian.com/cloud/jira-cloud-migration-assistant-guardrails-1026050480.html)
*Article based on support case *[https://appfire.atlassian.net/browse/SUPPORT-268569](https://appfire.atlassian.net/browse/SUPPORT-268569)* handled by *@Piotr Górzycki*.*
[https://appfire.atlassian.net/browse/DOCUM-4218](https://appfire.atlassian.net/browse/DOCUM-4218)