Streamlining Legacy Data Migration with the Getint App
Picture this scenario: Your company is undergoing a significant transition, whether it's a strategic move from Asana to Jira or the exciting acquisition of Company B by Company A. In these common use cases, the Getint app emerges as a vital tool, facilitating a seamless migration of legacy bugs, items, issues, and more. This transformation allows for the synchronization of parent items, tracking historical issues, and efficient management of your company's past, ensuring a smooth transition to a new operational landscape.
Migration Licensing:
As you embark on this migration journey with Getint, it's crucial to note that for Jira apps, the migration feature operates under a premium licensing model, billed separately from integrations. The premium feature ensures an advanced and tailored experience during data transfer, providing you with additional capabilities and support.
Before initiating migration, we recommend reviewing the licensing details for migrations to ensure a seamless and uninterrupted process. You can find comprehensive information about our premium licensing model on our official website or reach out to support@getint.io for personalized assistance.
1. Connecting for the First Time and Migrating:
Creating a Connection to Migrate:
Download and Open the Getint App: After downloading the desired Getint app, access it. You'll be prompted with the option to "Create an integration." Choose "Migration" from the pop-up window.
Integration Setup: Select the apps, create the integration, and map the issues and tasks along with their respective fields. Name and save the integration.
Configure Migration: Once the connection is created, configure the migration direction. Items will be recreated, updated, or skipped based on their existence.
Field Resync Options: The resync is only valid if you already did a previous migration and would like to fix issues, or migrate more fields. If that is the case, choose specific fields to resync during migration, such as Assignee, Status, Description, etc. You can add "_ALL_" to resync all fields or leave them blank.
Selective Migration: Optionally, fill in the IDs of the items to migrate or use JQL filtering for precision. (The JQL can be accessed by clicking the app logo in the integration. From there, you can create it at the integration level) The integration will be disabled by default after migration.
Set Time Range: Select a time range in the UTC timezone. Ensure the creation date of the issues falls within the chosen range, as this will be a trigger to migrate them. Note that Getint currently operates in the UTC timezone.
Schedule Migration: Click "Schedule Migration" to initiate the process. Depending on the volume of issues, it may take a few minutes to complete.
Continuous Sync Option: If you wish to enable continuous sync after migration, go to your integration screen, select "More," and tick the "Enable" box.
If you would like to enable continuous sync after the Migration, on your integration screen select “More” and tick the box “enable”.
2. Migrating on an Existing Integration:
If you already have a continuous sync in place and want to migrate older items, follow these steps:
Access Integration: Navigate to the integration you want to migrate items from. On the left side, select "Migrate Data." and follow steps 3-8 as explained above.
Enable Migration: Enable migration for the next run.
Field Resync Options: Choose specific fields to resync during migration, similar to the initial setup.
Selective Migration: Optionally, fill in item IDs or use JQL filtering for precision.
Monitoring Migration: Track the migration process by checking the "mode" tab, where "migration" will be displayed instead of "sync" once the process starts.
By default, the integration will be disabled after the migration. If you want the continuous sync to continue after the migration, be sure to select the box to enable that.
3. Benefits of Getint Migration Over Traditional CSV Import/Export:
When it comes to migrating your data during a significant transition, the Getint app offers distinct advantages over traditional CSV import/export methods. Here's why choosing Getint migration can elevate your data transfer experience:
Mapping and Integration with GetInt: GetInt provides a user-driven approach by allowing manual selection of types and fields for migration. Getint empowers users to customize the migration process, ensuring precision and control. This approach, distinct from traditional CSV import/export methods, allows users to save time, reduce errors, and maintain flexibility throughout the integration process.
Granular Field Resynchronization: With Getint, you have the flexibility to selectively resync specific fields, such as Assignee, Status, Description, and more. This level of granularity provides a targeted and efficient migration experience, surpassing the generic approach of CSV imports.
Selective Item Migration: GetInt allows you to choose specific items for migration using IDs or advanced filtering options like JQL. This targeted approach ensures that only the necessary data is transferred, enhancing efficiency compared to the bulk nature of CSV imports.
Real-time Monitoring and Continuous Sync: Unlike CSV imports that lack real-time monitoring, Getint provides a dynamic interface where you can track the migration progress. Additionally, the option for continuous sync after migration ensures that your data stays up-to-date effortlessly.
Integration with Existing Workflows: Getint seamlessly integrates into your existing workflows, providing a cohesive migration experience. This contrasts with CSV import/export, which may require additional steps to align with your established processes.
By choosing Getint migration over traditional CSV import/export methods, you not only streamline the migration process but also gain enhanced control, flexibility, and real-time insights into the transfer of your valuable data.
Last updated
