---
title: "Design"
slug: "connectivity-studio-design"
description: "Learn how to define integrations with connectors, documents, and messages for seamless data exchange between sources and targets like D365 and webshops."
tags: ["Introduction"]
status: "new"
updated: 2026-10-01T10:49:42Z
published: 2026-10-01T10:51:33Z
canonical: "docs.staedean.com/connectivity-studio-design"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Design

To define an integration with Connectivity Studio, these components are required:

- Two connectors A connector defines the type of connection and how to connect to the relevant data source.
- Two documents A document defines the data to be exchanged and its format and structure.
- One message A message is the carrier that transports data from a source to a target, based on the mapping as defined on the message. On the message you define:
  - The source information: the connector and document that is used for the data source.
  - The target information: the connector and document that is used for the data target.
  - The record mapping and field mapping that define which data goes where.

### **Example**

Import customers from a web shop to D365 F&SCM. In this case, the web shop is the source and D365 F&SCM the target. ![Diagram illustrating data flow from webshop to customers and D365 F&SCM system.](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/ExampleConnectivityBasics1.png)

For both the source (web shop) and the target (D365 F&SCM) a connector and a document are required. Also, a message is required to map the source and target data. ![Diagram illustrating data flow from source to target with connectors and documents.](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/ExampleConnectivityBasics2.png)

With this concept, all integrations are set up in the same structured way. You can also reuse components. For example, if you want to export customers from D365 F&SCM to the web shop, only a new message is required, and you can reuse the connectors and documents.