# Example syncs

**Data sync** workflows enable you to seamlessly orchestrate data between applications.

Synchronize any data between any two applications. For example:

* Sync part and BOM data between your PLM and ERP (for example, from [Teamcenter](/apps/t/teamcenter.md) , [Arena](/apps/a/arena.md) or [Windchill](/apps/w/windchill.md) to [NetSuite](/apps/n/netsuite.md), [SAP Business One (Coming Soon)](/apps/s/sap-business-one-coming-soon.md) or [Odoo (Coming Soon)](/apps/o/odoo-coming-soon.md))
* Sync purchase orders between your purchasing and accounting tools (like [Cofactr](/apps/c/cofactr.md), [Silkline](/apps/s/silkline.md), [ION](/apps/i/ion.md), [Boltline](/apps/b/boltline.md), [Ramp](/apps/r/ramp.md) and [QuickBooks](/apps/q/quickbooks.md))
* Sync inventory between your MES/MRP/ERP tools (for example [ION](/apps/i/ion.md), [Boltline](/apps/b/boltline.md), [Manufacturo](/apps/m/manufacturo.md), [NetSuite](/apps/n/netsuite.md)and [SAP Business One (Coming Soon)](/apps/s/sap-business-one-coming-soon.md)).

#### How does it work?

This powerful feature works by ingesting and mirroring data from a source app into Violet, then pushing it to a downstream tool that has a known, mapped data structure. 

Once a workflow is created, Violet will continue to push new changes to the target app when they occur.

You can configure rules for data syncs as well, for example only syncing parts that have a certain `Release` status, have a `Part Number` with a specific prefix, etc.

Read on for more info on some of our most popular automations:

<details>

<summary>PDM/PLM &#x3C;> MES</summary>

Save your engineering team valuable time by automating a typically manual task: pushing part data and assemblies from a PDM or PLM (like Teamcenter, Arena or Windchill) into your MES (like ION, Boltline or Manufacturo).

This automation is configurable in a number of ways:

* Configure rules for which parts you want to push, for example pushing only released parts or only certain projects
* Update revision scheme post-push to ensure consistency in your MES
* Populate fields in your MES (for example inventory tracking style or responsible engineer) based on attributes of the incoming part
* Push parts on an individual basis, or by default for everything in your PLM instance

Learn more about some of our most popular combos like [Teamcenter to ION](/features/workflows/data-sync-workflows/example-syncs/teamcenter-to-ion.md), [Arena to ION](/features/workflows/data-sync-workflows/example-syncs/arena-to-ion.md), and [Solidworks PDM to Boltline](/features/workflows/data-sync-workflows/example-syncs/solidworks-pdm-to-boltline.md).

</details>

<details>

<summary>PDM/PLM &#x3C;> ERP or Purchasing software</summary>

This automation pushes part data from your PDM/PLM to your ERP or Purchasing software to populate Inventory items, update Purchase Order data, attach relevant drawings, etc.

This automation is configurable in a number of ways:

* Push parts on an individual basis, or by default for your entire PLM instance
* Configure rules for which parts you want to push, for example pushing only released parts

Learn more about some of our most popular combos like [Teamcenter to NetSuite](/features/workflows/data-sync-workflows/example-syncs/teamcenter-to-netsuite.md) and [Teamcenter to Datum](/features/workflows/data-sync-workflows/example-syncs/teamcenter-to-datum.md).

</details>

<details>

<summary>Purchasing Data</summary>

This automation syncs purchasing data like Vendors, Suppliers, Purchase Orders and Receipts between software tools used for purchasing, inventory, MRP, ERP and more.

Syncs can be single direction or bi-directional, and scheduled or event-driven.

Common syncs include:

* Datum <> Quickbooks
* Precoro <> Boltline
* NetSuite <> ION

For a more advanced implementation, check out our [Inventory Engine](/features/inventory-engine.md).

</details>

<details>

<summary>Project Management &#x3C;> Scheduling</summary>

This automation syncs project management and scheduling data, ensuring a live link between project tasks and actual implementation.

Read more about our most popular combo: [Jira <> Smartsheet](/features/workflows/data-sync-workflows/example-syncs/jira-to-smartsheet.md).

</details>


---

# Agent Instructions: 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:

```
GET https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.