> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/licensing/seamless-transition-offer-migrate-from-competitors-to-getint-with-exclusive-benefits.md).
# Seamless Transition Offer: Migrate from Competitors to Getint with Exclusive Benefits
Migrate from Unito, Backbone, TFS4JIRA, ZigiWave, Jitterbit, ConnectAll or Workato.
In our mission to redefine integration solutions, Getint stands out by offering unparalleled value for your investment. Are you currently utilizing platforms like ConnectAll, Backbone, Exalate, Unito, Workato, TFS4JIRA, or other integration tools? We invite you to explore a game-changing opportunity with Getint. Reach out to us at \[contact information] to discover how we can assist in enhancing your integration efficiency while optimizing your budget.
Moreover, if you haven't committed to an integration tool yet, or if your integration partner uses one of these platforms, we're ready to present special offers tailored to ensure a smooth and cost-effective transition to Getint. Let's collaborate to streamline your workflows and achieve seamless integration across your tool ecosystem.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.getint.io/licensing/seamless-transition-offer-migrate-from-competitors-to-getint-with-exclusive-benefits.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
