---
title: "Customer replication"
slug: "bc-customer-replication"
description: "Learn to synchronize customer master data in D365 BC with XML publishing and subscription, ensuring accurate data management and traceability."
tags: ["BC", "BIS", "Business Central", "Business Integration Solutions", "Walkthrough"]
updated: 2026-06-25T09:59:07Z
published: 2026-06-25T09:59:07Z
canonical: "docs.staedean.com/bc-customer-replication"
---

> ## 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.

# Customer replication

This walkthrough provides an overview of how to synchronize customer master data.

In this replication scenario, the walkthrough demonstrates how to publish D365 BC data in a different XML structure and how to subscribe to it.

## Prerequisites

You can create two companies for demonstration purposes. In the following scenario:

- CRONUS International Ltd.: publishing company
- CRONUS Sales: subscription company

| Template | Description | Type | Company |
| --- | --- | --- | --- |
| TI_RM_CUSTOMER.OUT | STAEDEAN Template: Publish Customers for Synchronization | Publication | CRONUS International Ltd. |
| TI_RM_CUSTOMER.IN | STAEDEAN Template: Subscribe Customers for Synchronization | Subscription | CRONUS Sales |

## Publish customers template

### Story

This connection uses the following pipeline elements:

- The **Timer Event** triggers the pipeline.
- The **XML Generator** activity creates an XML file based on the internal document.
- A Mapper activity maps the internal document to an external document to export the D365 BC data in an external structure.
- The **File Writer** endpoint stores the created XML file at a specified file location.

![CO Pipeline](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerOut_Pipeline.png)

### Setup

1. Select the publishing company. ![Company - CRONUS International](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CRONUSInternationalLtd.png)
2. Import the Publication-TI_RM_CUSTOMER.OUT.zip configuration package. ![CO Import](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerOut_Import.png)
3. Open the TI_RM_CUSTOMER.OUT connection. On the connection page, edit the **File Writer** settings and enter the folder name. ![CO Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerOut_Settings.png)

### Process

1. Process the connection.
2. Check the output folder location.

### Result

![CO Results](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerOut_Result.png)

One XML file with a complete overview of your customers is created and available at the specified location.

## Subscribe customers template

### Story

This connection uses the following pipeline elements:

- The **File Reader** endpoint reads the published file from the file system.
- The XML file contains a complete list of customers. The **Splitter** activity creates one message per customer for proper traceability.
- The **Mapper** activity maps the external document to the internal D365 BC table structure.
- The **Record Generator** activity creates records and updates the D365 BC tables (Customer, Gen. Business Posting Group, and VAT Business Posting Group) based on the internal document.

![CI Pipeline](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerIn_Pipeline.png)

### Setup

1. Select the subscription company. ![Company - CRONUS Sales](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CRONUSales.png)
2. Import the Subscription-TI_RM_CUSTOMER.IN.zip configuration package. ![CI Import](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerIn_Import.png)
3. Open the TI_RM_CUSTOMER.IN connection. On the connection page, edit the **File Reader** settings and enter the folder name. ![CI Settings](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerIn_Settings.png)

> [!NOTE]
> **Note**
> 
> The **File Reader** endpoint includes typical Replication Management properties: **Leave File on File System**, **Read New Files Only**, and **Last Processed at**. In many cases, the internal document from the publication connection can reuse for the subscription connection.

### Process

1. Process the connection.
2. Check the Transaction Log to see more details.

### Result

![CI Results](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/DM_CustomerIn_Result.png)

The customers are imported. You can also use the **Transaction Log** to see more details for each import.

## Related

- [Vendor replication](/bc-vendor-replication.md)