Migrating Data with Getint
Last updated
Was this helpful?
Last updated
Was this helpful?
Migrating data between project management tools is a critical step in ensuring seamless transitions during tool changes, company mergers, or acquisitions. Whether you are moving from Azure DevOps, ServiceNow, Asana or Monday to Jira, or the other way around, consolidating multiple Jira instances, or onboarding Company B’s project data into Company A’s system, Getint’s Migration Feature ensures a smooth and structured transfer of historical issues, tasks, bugs, and more.
Unlike traditional CSV export/import, Getint’s migration offers granular control, automation, and real-time monitoring, eliminating manual errors and data inconsistencies.
Migration is a premium feature and is billed separately from continuous integration. This ensures an advanced migration experience with enhanced customization, support, and additional features.
Before starting your migration, review our for detailed licensing options. If you have any questions, reach out to our
To ensure a smooth migration, consider the following:
Ensure Matching Fields Exist: If your source system includes fields that do not exist in the destination system, you must create them beforehand. This ensures that 1:1 field mapping can be applied where necessary.
Handling Fields That Cannot Be Mapped: If some fields cannot be mapped directly, you can still migrate their values. Create a custom text field on the destination tool and map the original field to it, enabling the "Use label from the other side" option. This will transfer the field's value as plain text without requiring a matching field type.
For advanced use cases, it is also possible to migrate values from multiple source fields into a single text field using a merging option or, if necessary, a custom script. This can be useful when a 1:1 mapping is not required or feasible. For more information on how to merge fields, follow our guide .
For more tips, refer to .
Open the Getint App and select Create an Integration.
In the pop-up window, choose Migration as the integration type.
Map issue types, according to your needs, between the two systems.
Ensure that the fields are mapped correctly. Follow our guides for each app integration to ensure proper mapping.
Name the integration and save the configuration.
The migration will be created but disabled by default; its status will change once the settings are properly configured.
With the integration properly configured, it is now time to set the migration. Go to the Migrate Data tab and Enable the Migration on the next run.
Select Migration Direction: Define if the items from the app on the left will be migrated to the right or from the app on the right to the left.ft
Decide on what to do with the items already migrated: Define whether items will be recreated, updated, or skipped if they already exist in the target system.
Field Resynchronization (Optional): If you’ve previously migrated data and want to update specific fields (e.g., Assignee, Status, Description), specify them here. To resync all fields, enter _ALL_ or leave the field blank.
Selective Migration (Optional):
Provide specific item IDs for migration.
Set a Time Range: To filter which items should be migrated, select the creation date or the last updated date in UTC.
Start the Migration: Click Schedule Migration to begin the process. Migration time depends on the volume of data.
Getint will be in migration mode. Monitor progress in sync logs to ensure a smooth transfer.
Enable Continuous Sync (Optional)
If you want newly created issues to continue syncing after migration:
Disable the option to stop the sync after the migration.
Or change the settings after the Migration:
Go to your integration, click More >Settings> Enable.
By default, the integration is disabled after migration to prevent unintended updates.
If you already have a continuous sync in place but need to migrate older items, follow these steps:
Open the Getint App and navigate to your existing integration.
Select Migrate Data from the left-hand menu.
Configure the migration settings as described in the previous section.
Enable migration for the next sync run.
Monitor progress on the latest runs and logs.
Many companies use CSV exports/imports for migration, but Getint’s Migration Feature provides several advantages:
Getint allows users to manually map issue types and fields, ensuring precise data transfer.
Traditional CSV imports require rigid predefined templates, making data structuring complex.
With Getint, specific fields can be resynced on demand, preventing unnecessary updates.
CSV imports lack flexibility—you must re-import everything or risk data loss.
Getint lets you filter specific items by ID or JQL queries to migrate only what’s necessary.
CSV methods require manual filtering and do not offer dynamic selection.
Getint provides live tracking of migration progress with sync logs.
Traditional CSV methods lack real-time updates—errors may go unnoticed until post-import verification.
Getint migration works alongside existing integrations, allowing continuous sync post-migration.
CSV imports often overwrite or duplicate data, requiring additional cleanup.
By choosing Getint’s Migration Feature, your organization benefits from precision, automation, and full control over the migration process.
Select the apps involved in the migration. We recommend checking our documentation to review how to create the integrations: .
Use JQL filtering for more refined data selection. JQL filters can be accessed by clicking the app logo in the integration. You can find more details on filtering in our guide: .
For additional support, visit our .
Considering migration? with our team to explore how Getint can support your transition.
