Getint Migration Guide – Best Practices & Preparation
When moving from Server or Data Center to Jira Cloud (or between tools with Getint integrations), planning is everything. From what we saw at NEXP and from our own experience with migrations, here's what our customers need to know and do.
Your migration license includes a 3-month sync license, giving you time to test the tool, understand how it works, and prepare your setup. There's no need to migrate data immediately. Use this period to validate your configuration and plan a gradual, well-structured migration. Skipping this step can lead to issues that are easily avoided with proper preparation.
1. What Customers Must Know Upfront
Migrations take time: Even small setups require weeks of planning and testing; larger ones may take months.
Costs go beyond licenses: Budget for app replacements, support, and potential consulting hours.
Not all apps migrate smoothly: Some on-premise apps don't exist on Cloud or behave differently — we’ll help you map alternatives.
Integrations are critical: If you rely on Salesforce, GitHub, ServiceNow, or others, these must be accounted for from day one.
User adoption is as important as data migration: A technically successful migration can fail if users aren’t prepared.
2. How to Plan with Getint
Step 1 – Define your goals
Why migrate? Cost savings, Atlassian support deadlines, scalability, better collaboration?
Be clear on priorities so the migration plan matches your business needs.
Step 2 – Audit Your Current Setup
Review projects, workflows, custom fields, and automations.
List all apps in use and mark which are critical vs. "nice-to-have."
Map all external systems that connect to Jira.
Step 3 – Budget & Timeline
Plan for phased migration (waves).
Include costs for apps that need replacements.
Expect extra time for clean-up and user training.
Step 4 – Communication Plan
Identify your internal champions.
Create a channel for migration updates and questions.
Let users know what changes to expect and when.
3. Best Practices During Migration
Start small: Run a pilot migration with one project/team before moving everything.
Clean before you move: Archive unused projects and standardize workflows to simplify the transition.
Test more than once: Run dry migrations to validate data accuracy and permissions.
Have a rollback plan: Always know how you’ll recover if something fails.
Document everything: Track what’s moved, what's pending, and any issues found.
Use the sync license to test the tool: A sync license is included with your migration and remains active for 3 months. We recommend using this time to thoroughly test the tool, get familiar with its features, and ensure everything is working as expected before running your full migration. Starting the migration without a solid understanding of how Getint works can lead to avoidable issues down the line.
4. What Not to Do
Don’t underestimate app compatibility — this is the #1 issue in every migration.
Don’t leave communication for the last minute. Silence creates frustration.
Don’t try to "lift and shift" everything at once.
Don’t rely only on IT — involve business teams who know the workflows.
Don’t ignore integrations — migrations fail if critical connections aren’t mapped and tested.
5. Preparing Your Team
Training: Run short workshops on Jira Cloud differences before go-live.
Support Presence: Have a clear escalation path with Getint and your own IT team.
Onboarding aids: Provide quick guides, FAQs, or even AI assistants like Rovo to help with "how do I…" questions.
Post-migration check-ins: Schedule follow-ups after each wave to collect feedback and fix issues.
6. Time & Cost Expectations
Timeline:
Small teams: 4–6 weeks with preparation + testing.
Medium setups: 2–3 months.
Large/complex (multiple tools + apps): 6+ months.
Costs:
Jira Cloud licenses.
App replacements or upgrades.
Migration support hours (internal + Getint consultants if needed).
Training and change management.
7. How Getint Supports You
Assessment: We help audit your setup, identify risks, and recommend alternatives.
Phased approach: We plan waves with you, not a risky all-in-one move.
Integrations expertise: We ensure Salesforce, GitHub, ServiceNow, Azure DevOps, etc., continue to work seamlessly.
Hands-on support: Our team is available during and after migration, not just for issues but to guide best practices.
Post-migration optimization: We check integrations, workflows, and performance once you're live.
8. Quick Checklist
✅ Define goals & align leadership. ✅ Audit apps, workflows, and integrations. ✅ Budget for more than licenses. ✅ Plan phased migration waves. ✅ Run test migrations & validate data. ✅ Prepare a rollback plan. ✅ Train and support users before go-live. ✅ Monitor and optimize post-migration.
If you have questions about pricing or need help with the migration process, please submit a ticket through our support portal. We're happy to assist.
Last updated
Was this helpful?