Dr. Ankita Mehta-OpsHub, Inc Atlassian Partner

Hi @Jean Dupree Hitting these limits with Aha! to Jira migrations is common scenario. A few things worth thinking through as you evaluate options: * Scope and depth of data: Decide upfront whether you’re moving just active work or also historical items, including comments, attachments, votes, links, and relationships. That…

Hi @nikki SM has request types, SLAs, customer fields, and portal-specific configurations that don’t exist natively in Jira Software, so tickets won’t migrate cleanly unless those gaps are addressed first. Successful migrations usually involve some restructuring rather than a direct lift and shift. A few things to…

Hi @John Black This usually causes confusion because JSM Cloud includes the Jira platform, but the site must have the base Jira product provisioned correctly before migration. A few things to check: * Ensure the Cloud site was created as a JSM site (not just a user subscription added later). * Confirm the base Jira…

Hi @Veerapindi Satyanarayana SSO setups for Jira DC and Cloud can feel a bit different at first. The basics are similar, but the flow and where things get configured do change between the two. A few things worth keeping in mind as you plan this out: * Jira DC typically uses SAML with Azure AD/Okta/Ping, while Jira Cloud…

Hi @Digambar Prakash Dhanagar As rightly mentioned in the above answer. the app-based custom fields only come across if the same plugin exists on the target, and Jira will drop those fields completely during an XML restore if the app isn’t available. A few things to consider as you work through this: * XML restore requires…

Hi @Prabakar Welcome to the Atlassian Community! Moving projects between separate Atlassian organizations can be tricky because the native Data Transfer option doesn’t support cross-org migrations. Here are a few things to consider: * Permissions & access: You’ll need admin access in both organizations to perform the…

Hi @Sudarsana G Shifting from Team-managed to Company-managed projects can really help with consistency and governance, but there are a few details worth sorting out before you start. Here are a few things to consider: * Fields and workflows: Team-managed projects use their own isolated configurations, so you’ll need to…

Hi @khushboo_puri That’s a huge migration, and with 25,000 projects and over 23 million issues, it’s the one that needs careful planning and a well-thought strategy. At that scale, the key isn’t just the tool - it’s how you break down, stage, and validate the move so that teams stay productive throughout. A few things to…

Hi @David Yu The old DVCS connector did rely heavily on API polling, so performance dropped fast with larger repo counts. The newer webhook-based setup in Jira Cloud is better, but there are still a few things to keep in mind: * API rate limits: Even with webhooks, some Jira actions still trigger GitHub API calls, so large…

Hi @Ali Ali Migrating from Server to Cloud isn’t hard, but keeping your workflow logic intact does need a bit of prep. Since those custom workflows sound like the heart of your process, here are a few things to keep in mind before you begin: * Workflows: Most statuses and transitions migrate fine, but anything tied to…

Hi @Noble Sengar Don’t worry -your Server license will stay intact. Running a migration or even testing it won’t deactivate or affect your on-prem instance. As Jayesh mentioned, it’s a good idea to spin up a sandbox Cloud site and use it for validation. That way, you can safely check how your projects, workflows, and…

Hi @John Funk , Yeah, that’s doable but not as straightforward as it sounds if you’re relying only on Jira and Salesforce APIs. You’ll need something that can handle the data mapping, trigger logic, and sync cleanly without custom code. Here are few things to consider: * Data mapping: Identify which Salesforce fields (like…

Hi @Jeremy Wood The native GitHub–Jira connector is great for quick setups but limited when it comes to governance and access control. A few things to think about before you pick an alternative: * Repository-level control: Look for a solution that lets you explicitly choose which GitHub repos link to which Jira projects,…

Hi @RAJ Patil As far as I know, the MCP endpoint is still primarily geared toward Atlassian’s own AI and internal service integrations, so external apps can run into a few limitations. * Protocol compatibility: MCP uses a server-sent events (SSE) stream, which Salesforce doesn’t handle natively without a middleware layer.…

Hi @Katherine Lord During migration, duplicate or mixed accounts often show up. The key is to clean them up during migration, not after. Some points to consider: * Transform on the fly: Most tools will force you to migrate users as @A.com first, then bulk update them to @B.com inside Jira. This will make all issues updated…

Hi @Sebastian Krzewiński If you’re thinking about exporting Jira data to Snowflake, there are a few things to consider first: * Which projects and fields you actually need. * Whether you need historical data or just current issues. * How often the data should update — one-time export vs. ongoing sync. * Handling…

Hi @Julia Watson-Clarke Yes, that should be possible, but there are a few things to consider. * Mapping the field: You’ll need to make sure your Jira custom field is included in the integration mapping so that HubSpot can push the RAG status to Jira. * Field type compatibility: Check that the field type in Jira (e.g.,…

Hi @ena.egbe If you want your customers to see Jira data in HubSpot without giving them access to your internal Jira, there are a few things to think about first: * What data matters: Only sync the tickets, comments, or fields that are relevant to customers. * Permissions & visibility: Make sure sensitive internal info…

Hi @Zack Lathan When you’re syncing HubSpot tickets to Jira, especially with custom fields, it helps to think through a few things first: * Which fields really matter for your workflow — just because a field exists doesn’t mean it needs syncing. * Field types and formats — picklists, dates, multi-selects can behave…

Thanks for the clarification, @Tanguy Crusson

Hi @Suresh Sakhare Are you seeing empty fields like Description or custom values after bulk moving from a Team-managed to Company-managed project? If you are, it's not uncommon, and here are a few things to consider pinpointing the root cause: * Fields might be missing from the CMP screen configuration. Even if the field…

Hi @Beatriz Figueiredo Thanks for bringing this up — you're highlighting pain points that many teams quietly struggle with during ADO to Jira migrations. Before starting the migration, it’s important to think through how the data will be structured and used once it's moved. Here are a few things to consider: * CSV is a…

Hi @Hemal Jivani You're right, embedding JSM into a native app while controlling access, ensuring smooth login, and maintaining a two-way sync isn't straightforward. Here are some key points to consider before you begin: * Portal Embedding: Often buggy in native apps; SSO and customization are limited. * Access Control:…

Hi @Mau Jimenez When alert-to-ticket workflows break, the issue usually lies in how synchronization is set up, not just creation triggers. Here are some things to consider before you begin: * State mismatch: Alert and issue statuses may not be mapped 1:1 (e.g., “Work in Progress” not updating alert to “Acknowledged”). *…

Hi @Sreenivas Kunde Migrating from Jira Server to Cloud can sometimes throw errors, often due to differences in workflows, custom fields, or user mapping between environments. A few things to check: * App and field compatibility * Custom workflow or issue type mismatches * User mapping across environments * Permission and…

Hi @Salvatore Di Franca Migrating a Jira project between two Atlassian Cloud orgs is doable and with the right tool, it can be smooth and low risk. The key is to think beyond just moving issues, and evaluate how well the migration preserves structure, context, and continuity. Here are a few important things to consider…

Hi @emily.scheer The new hierarchy features in JPD Premium definitely simplifies things. However, there are few things to consider: * Depending on how much data you’ve built up, this could be a light cleanup or a more involved effort — and during this time, teams may experience some disruption or downtime, especially if…

Hi @Andreas Gade Hjarnø Losing connection between Jira and Bitbucket can be frustrating, but there are a few common things to check that often help: * API access and permissions — Sometimes tokens expire or permissions change without notice, so it’s good to verify Jira still has proper access to Bitbucket. * Service status…

Hi @jennifer_mitchell If your Jira tickets suddenly stop showing branch or PR info but nothing’s changed with connectors or permissions, here are a few things you can check: * API tokens and permissions — Sometimes tokens expire or lose some access without obvious changes, so double-check those just in case. * Service…

Hi @Gil Nadav When encountering intermittent integration issues like GitHub PRs not syncing properly with Jira tickets, it’s important first to consider several factors: * Check if there are known outages on the platforms involved, * Review recent changes in API limits or authentication, and * verify if any recent updates…