Migrating project data from a self-hosted Jira Server to Atlassian Cloud without creating custom fields in the target system, but instead importing the custom field data as attachments, is an unconventional approach. However, it can be accomplished with careful planning and execution. Here's a strategic plan to achieve this:
1. Prepare Data
Extract Data: Pull custom field data from Jira Server.
Format Data: Convert the data into a file format (e.g., CSV, JSON) for each issue, naming files to correspond with their related issues.
2. Automate Attachments
Script Development: Write a script (preferably in Python) to automate uploading these files as attachments to the corresponding issues in Jira Cloud using the Jira Cloud REST API.
Parallel Processing: Implement parallel processing in your script to handle bulk operations efficiently, ensuring you stay within API rate limits.
3. Execution
Test First: Run your process in a staging environment to catch any issues.
Monitor and Validate: Keep an eye on the import process and verify the data accuracy post-migration.
Key Considerations
API Limits: Be aware of and plan for Jira Cloud's API rate limits.
User Impact: Understand that accessing data in attachments won't be as seamless as with custom fields.
This approach is practical for a bulk import of 10,000 records and emphasizes efficiency, planning, and testing to ensure a smooth migration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.