# Getting started introduction

## Introduction

Having registered for a Patchworks account and logged into the dashboard, you're all set to start syncing data between your business-critical systems. There are two ways to approach this: &#x20;

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2Fn96PB7zIrlFujAqZSnGz%2Fold%20versus%20new%20approach%20-%20services%20%26%20flows.png?alt=media&#x26;token=82a0da4c-0150-4d2e-b499-d0bd6c498f2a" alt="" width="563"><figcaption></figcaption></figure></div>

If you registered for a Patchworks account before July 2023, you'll be familiar with using [services](https://app.gitbook.com/s/5mpqoXPMbUuPa8JpCLWe/getting-started/what-is-a-service) to sync data between systems. Process flows include all the functionality of services and much more. You can continue to use services but if you'd like to try [process flows](#process-flows), please contact your Customer Success Manager, or reach out to <customersuccess@wearepatchworks.com>. \
\
If you registered for a Patchworks account after July 2023, you will be using [process flows](#process-flows) automatically.

## Process flows

**Process flows** are a new, incredibly powerful tool that you can use to define smart, flexible flows to exchange data between connector [instances](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/working-with-instances). Process flows are built by dragging and dropping [shapes](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes) onto a [canvas](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/the-process-flow-canvas), and then configuring those shapes to work in the way you need. \
\
Please take a look at our [Patchworks quickstart guide](https://doc.wearepatchworks.com/product-documentation/getting-started/patchworks-quickstart-guide) to get your bearings, and then navigate to the [process flows](https://doc.wearepatchworks.com/product-documentation/process-flows/about-process-flows) section of this documentation for more detailed information.

## Services

If you are an existing customer, you'll be familiar with the concept of using **services** to exchange data between two **system connectors**. If you're not ready to make the switch to [process flows](https://doc.wearepatchworks.com/product-documentation/process-flows/about-process-flows), that's OK - please see the [services](https://app.gitbook.com/s/5mpqoXPMbUuPa8JpCLWe/getting-started/what-is-a-service) section of this documentation for information that's relevant to your way of working.

## In this section <a href="#in-this-section" id="in-this-section"></a>

* [Core subscription tiers](https://doc.wearepatchworks.com/product-documentation/getting-started/core-subscription-tiers)
* [Key concepts & terminology](https://doc.wearepatchworks.com/product-documentation/getting-started/key-concepts-and-terminology)
* [Multi-language support](https://doc.wearepatchworks.com/product-documentation/getting-started/multi-language-support)
* [Patchworks quickstart guide​](https://doc.wearepatchworks.com/product-documentation/getting-started/patchworks-quickstart-guide)
* [Patchworks infrastructure](https://doc.wearepatchworks.com/product-documentation/getting-started/technical-overview/patchworks-infrastructure)

​
