> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/shopware/shopware6_en_us/customer-management/customer-upload-bc-to-shopware.md).

# Customer Upload (BC to Shopware)

Customers can be transferred from Business Central to Shopware, for example to provide B2B accounts with stored terms and conditions there.

**Prerequisite**

The customer must be flagged as a **web customer** (`SOUSHW Web Customer = Ja`). Only then is the upload available.

**Mandatory information (checked before upload)**

Before the upload, the connector checks the following, among other things:

* Email address and name
* **Customer group** (`GroupId`)
* **Salutation** (`SalutationId`)
* **Sales channel**
* **Country/region mapping**

{% hint style="warning" %}
If any of this information is missing, the upload is canceled with a message. Maintain the mappings for salutations & countries and for customer groups first.
{% endhint %}

**Procedure**

{% stepper %}
{% step %}
**Prepare the customer**

Set **Web Customer = Yes** and maintain the customer group, salutation, and sales channel.
{% endstep %}

{% step %}
**Upload**

Open the Customer Card and choose **Upload Customer**. Once successful, the **Web-ID** is filled in.
{% endstep %}

{% step %}
**Follow-up synchronization**

The **ship-to addresses** and, if applicable, the **customer price list** are then synchronized automatically.
{% endstep %}
{% endstepper %}

**Fields on the Customer Card**

| Field                                       | Meaning                             |
| ------------------------------------------- | ----------------------------------- |
| Web-ID                                      | Shopware customer ID (after upload) |
| Web Customer                                | Flagged for upload                  |
| Sales Channel / Salutation / Customer Group | Mapping values                      |
| Account Type                                | Business or Private                 |
| Synchronized / on / Message                 | Sync status                         |

{% hint style="info" %}
If a customer is changed, it is automatically flagged as *not synchronized* and transferred again during the next run.
{% endhint %}

### Frequently Asked Questions

#### Which endpoint is used to transfer customers and addresses?

Customers are created (POST) or updated (PATCH) via `customer`, and ship-to addresses via `customer-address`. After a successful upload, the "SOUSHW Web ID" is set on the customer and – if one exists – the customer price list is synchronized afterwards automatically.

#### Which information must be maintained before the customer upload?

Before the upload, the connector checks the email address and name as well as the mappings for customer group (`GroupId`), salutation (`SalutationId`), sales channel, and country/region. If any of this information is missing, the upload is canceled with a message – maintain the corresponding mappings first.


---

# 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.solutioo.de/shopware/shopware6_en_us/customer-management/customer-upload-bc-to-shopware.md?ask=<question>&goal=<user_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.