> 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/getintio-platform/syncing-many-to-many-projects.md).
# Syncing Many to Many Projects
This document provides best practices for handling many-to-many projects in Getint, where a single or multiple projects must synchronize with other target projects across apps.
The **Sync many projects** option is currently available for **Jira**, **Azure DevOps**, **Monday.com**, and **Asana** connections. When enabled, only these apps appear as the second side of the integration: **Jira**, **ServiceNow**, **Azure DevOps**, **Monday.com**, and **Asana**.
### Choose the Sync Mode Before You Build the Integration.
If you do not tick **Sync many projects** while setting up the connection, that side of the integration stays locked to the single project you selected. The option cannot be enabled later, so adding a second project means building a new integration from scratch.
The reverse does work. An integration created with **Sync many projects** enabled can be reduced to a single project, although the interface continues to display the many-project layout and Item Routing has to be updated to match the new selection.
{% hint style="warning" %}
**ServiceNow Integrations:**
When configuring many-to-many sync with ServiceNow, "Sync many projects" is available **only on the source app side** (i.e., Jira).
Getint connects to the **entire ServiceNow instance** (not individual projects), so configure **Item Routing** in the source app to direct tickets from ServiceNow.
{% endhint %}
### How to Sync Many Projects
1. To synchronize multiple projects, begin by creating an integration as you normally would. Next, choose Jira as the connector on the left side.
2. Next, either select an existing connection or create a new one. After the connection is set, you’ll see a checkbox labeled **Sync many projects** above the dropdown list.
3. Select the projects you want to sync, then click **Connect**.
{% hint style="info" %}
An **X** appears next to each project name. Click it to remove a project from the selection if you chose the wrong one.
{% endhint %}
4. Select the counterpart application—in this example, Jira. Then repeat the previous steps to choose the projects you want to sync.
{% hint style="warning" %}
Unlike many-to-many project syncing, Jira-ServiceNow integrations only require selecting many projects from the Jira side. ServiceNow lacks individual projects, so we connect to the **entire instance** (not specific boards).
{% endhint %}
5. Click **Start with Mapping Types** to map the work item types.
6. After mapping issue types, you can start adding fields to them. At the time we’re publishing this article, the **Quick Build** feature is not available for many-to-many projects. You will need to map fields manually.
#### Defining Conditions in Items Routing
The next step is to define conditions, as routing refers to the path a work item takes across connected systems. By setting clear rules, you ensure Getint knows which project each incoming work item belongs to and what type it should have.
Please follow the next steps to set up the rules for syncing your items, and then review the subsequent configuration steps to confirm that transitions, field mappings, and workflows are properly aligned.
{% hint style="warning" %}
Item routing must be defined on both sides; otherwise, work items will not sync.
{% endhint %}
1. Please select the project where the item will be routed and specify its issue type. In this example, we are configuring how items from the right side will sync into the corresponding project on the left.
2. Choose the field that will trigger the sync. For example, click **+Add New Field** to add conditions across multiple fields. If all conditions are met, the item will sync to the project you are routing it to.
3. Now repeat the same steps for the right side of the integration. In this case, you are defining how items from the left will sync into the corresponding project on the right as long as conditions are met.
4. Click **Apply** to submit the changes, then save the integration. After that, test the integration to confirm that routing works correctly and items are syncing as expected.
#### Removing or Adding Projects to Existing Integrations
You may need to adjust the projects connected to an integration. This can involve adding new projects to expand its scope or removing existing ones to simplify or restructure it. Follow the steps below to make these changes:
* Click the box for the side of the app you want to modify. You can choose either side, depending on your goal.
* Use the dropdown list to browse your projects and add new ones. You can also remove projects from the integration by clicking the **X** icon next to the project name. This works the same way as when you added or removed projects during the initial setup.
* Close the tab and save the integration to submit your changes.
{% hint style="warning" %}
You need to define new conditions to route work items to any new project you've added.
{% endhint %}
#### Switching Between Single Project and Many Projects Syncs
The **Sync many projects** option can only be enabled while you are setting up the connection. Moving between the two modes works in one direction only.
**Single project to many projects is not possible**: An integration built without **Sync many projects** stays tied to the project selected on that side, and the checkbox is no longer available once the integration exists. To cover additional projects, create a new integration with the option ticked, then rebuild the type mappings, field mappings, and routing conditions. After testing the replacement, disable or delete the original integration.
**Many projects to a single project does work**: Follow the steps in the previous section and remove projects until one remains on that side. Two points to keep in mind:
* The interface still looks like a many-project sync. The checkbox stays ticked, and the project field continues to behave as a multi-project selector, even though only one project is selected.
* Item Routing has to be updated to reflect the change. Conditions that pointed to the removed projects no longer resolve, so review the rules on both sides and adjust them so that every work item routes to the remaining project.
Because the restriction only applies in one direction, tick **Sync many projects** during setup whenever there is a chance that more projects will join the sync later, even if you start with a single project on each side.
{% hint style="warning" %}
Work items will not sync while Item Routing still references a project that has been removed from the integration. Update the conditions on both sides before saving.
{% endhint %}
### Conclusion
Managing integrations is not a one‑time task but an ongoing process. Whether you are adding new projects to expand collaboration or removing existing ones to simplify workflows, the key is to define clear routing conditions and test thoroughly. By carefully mapping fields, setting rules, and validating sync behavior, you ensure that work items flow correctly between systems.
Need more help? Visit our [Help Center](https://getint.io/help-center) or reach out to support by clicking the chat bubble for direct assistance.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.getint.io/getintio-platform/syncing-many-to-many-projects.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
