# Migration vs Integration

{% hint style="warning" %}
Migration is a premium feature that is limited during the trial version. For detailed pricing information based on the volume of tasks, visit [Getint Pricing](https://www.getint.io/pricing) and click on **Migration.**
{% endhint %}

### Data Migration

#### Definition and Use Case <a href="#definition-and-use-case" id="definition-and-use-case"></a>

Data migration in Getint refers to the process of moving historical data—the information that existed before you started using Getint. This is crucial when transitioning from one tool to another, ensuring that all records are preserved. Typical use cases involve migrating data from one platform to another, such as:

* Jira to Azure DevOps
* Asana to Jira
* ClickUp to Monday.com

#### Project Nature <a href="#project-nature" id="project-nature"></a>

Migration projects are generally one-time operations designed to move a large volume of data within a limited timeframe. This process ensures that historical data is seamlessly transferred to the new system, maintaining the continuity of your workflows.

### Continuous Sync <a href="#data-integration" id="data-integration"></a>

#### Definition and Use Case <a href="#definition-and-use-case.1" id="definition-and-use-case.1"></a>

Data integration connects newly created or recently updated items—tasks, service requests, bugs, etc.—in real-time or near real-time. This ongoing process begins the moment you start using Getint, keeping your systems synchronized as new data is generated.

#### Project Nature <a href="#project-nature.1" id="project-nature.1"></a>

Integrations are typically long-term, ongoing projects. They involve syncing smaller batches of data regularly, often daily. Integration is essential for maintaining continuous data flow between different platforms as updates and new items are created.

### Combining Migration and Integration <a href="#combining-migration-and-integration" id="combining-migration-and-integration"></a>

Some projects require both: initially migrating historical items and then continuously syncing new updates or creations. This approach ensures a comprehensive transition to a new system, followed by consistent and up-to-date synchronization moving forward.

### Pricing Models <a href="#pricing-models" id="pricing-models"></a>

* **Migrations:** The cost is based on the **volume of tasks** to be migrated.
* **Integrations:** For integrations involving Jira, pricing is based on the number of Jira users, and billed via the [**Atlassian Marketplace**](https://marketplace.atlassian.com/vendors/1218845/getint-integrations-jira-azure-devops-servicenow-salesforce-asana-monday-clickup-gitlab-and-others). Non-Jira integrations are billed through us directly, and they are available in three different plans:
  * **Unlimited $1,800/year - Supported Tools:** ClickUp, Monday, Asana, GitLab, GitHub, Wrike, Hubspot, Zendesk.
  * **Professional $4,800/year - Supported Tools:** ServiceNow, Salesforce, Azure DevOps.
  * **Enterprise - Custom Pricing:** An unlimited number of tools are supported.

### Setup Process <a href="#setup-process" id="setup-process"></a>

The setup for both migration and integration is nearly identical in Getint. For migrations, additional steps include enabling the migration feature, specifying the direction (source and target systems), and defining the time range for the issues to be migrated.

<figure><img src="https://4106311246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MR6Z9V8zLATPQPOGSDf%2Fuploads%2F9OSEDBl869gRue9mQAwv%2FGetint%20Yellow%20Banner.png?alt=media&#x26;token=9cc42142-6e48-4931-8fd5-cbf7dcf4cdc1" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>