Migration Guides
The Migration feature in Getint allows users to efficiently transfer data between applications, ensuring seamless transitions while maintaining data integrity. Whether you're switching from one platform to another or need to migrate specific items as part of a larger workflow, Getint provides a structured and flexible migration process.
In this guide, you'll learn how the migration feature works, how to test it during the trial period, and key considerations for a smooth data migration experience.
Looking for step-by-step migration instructions? Choose a specific migration tutorial from the left menu.
How Migration Works in Getint
Key Features of the Getint Migration Tool
Trial Limitations: The migration feature has limitations during the trial period but can still be tested (details below).
Full Access on Request: To unlock full migration capabilities, users must request access and purchase the feature.
Advanced Migration Options:
Time-Range Selection: Migrate items created or updated within a specific period.
Directional Migration: Choose the source and target applications for migration.
Handling Existing Items: Select whether to:
Skip previously synchronized items.
Recreate existing items.
Update existing counterparts in the target app.
Migration Mode vs. Standard Integration
When the migration feature is enabled, the next integration run operates in Migration Mode, ensuring smooth data transfer.
Type Mapping and Field Mapping: Migration follows the same type and field mapping configurations as a regular integration run.
Optimized Performance and Reliability
Migration operations can be resource-intensive and time-consuming.
To ensure a smooth experience, Getint runs migrations in a dedicated environment, keeping live integrations unaffected.
How to Test the Migration Feature During Trial
During the trial period, the migration feature is limited, but testing is available under the following conditions:
Users have access to 20 migration test runs.
Each test run can migrate up to 5 items.
This allows businesses to evaluate migration functionality before purchasing full access.
Need help testing migration? Visit our Support Portal for assistance.
Why Getint Migration is Better Than Standard CSV Import/Export
Unlike traditional CSV export-import methods, Getint offers a much more efficient, accurate, and automated migration process:
✅ Real-Time Synchronization – Unlike CSV imports, which require manual updates, Getint keeps your data continuously in sync. ✅ Preserves Issue History & Relationships – Getint migrates full data structures, including attachments, comments, and custom fields. CSV imports often fail to retain relationships. ✅ Error Prevention & Smart Mapping – Getint ensures precise field mapping and prevents data mismatches, reducing errors compared to manual CSV handling. ✅ No Manual Intervention Required – CSV imports require manual exports, format corrections, and imports, while Getint automates the entire process seamlessly. ✅ Works with Complex Workflows – Supports advanced migration rules, such as filtering, transformation, and incremental updates, which CSV lacks.
For an in-depth Jira migration process, refer to our Master Jira Migration with Getint – Your Ultimate Guide.
Pricing for the Migration Feature
Getint’s migration pricing is based on the volume of issues, tasks, or incidents you need to migrate, ensuring flexibility and scalability for businesses of all sizes. Unlike our regular licensing model, migration pricing is not based on Jira users or an annual fee. Instead, it is structured as a 3-month migration license, allowing enough time for thorough planning, execution, and validation of the migration process.
Pricing Tiers
Up to 2,000 issues/tasks/incidents → $1,500
Up to 20,000 issues/tasks/incidents → $3,000
Custom Pricing → Contact our team for a tailored quote on migrations exceeding 20,000 items, including large-scale migrations of up to 1 million tasks.
View our pricing page for more details or reach out to our Support Team for assistance.
Last updated
Was this helpful?
