The Cloud Replicator enables you to replicate your Microsoft Dynamics 365 Business Central data to different cloud databases. While replicating it’s possible to transform your data to be easier to use for reporting with tools like Power BI.

This image has an empty alt attribute

The Replicator supports the following cloud storage services:

  • Azure Table Storage
  • Cosmos DB Table API
  • Cosmos DB Core API

Key features of the cloud replicator:

  • Aggregate data from multiple companies from a single or many tenants into a single database, making it easier to do cross-company reporting
  • Support daily increments replications loads to reduce replication time
  • Replication engine with up to 100 parallel tasks running (per tenant)
  • Flatten table structures
  • Populate all dimensions on transactional tables


The Cloud Replicator setup is straightforward. You must specify how many replication engines you want. This will determine how fast you can replicate data. If you have 10 tables and 10 companies, that’s 100 replication jobs. If you specify 25 engines, then each engine will receive 4 jobs to execute. More engines mean faster replication, but more engines also mean more server resources are needed. Check here for the current limits in Cloud Business Central.

This image has an empty alt attribute
Cloud Replicator Setup

Add each tables you want to replicate to the table mapping. The Company Filter field is a filter of what companies to include. Blank means all companies. Otherwise specify what companies to replicate, separated with | (like Cronus US|Cronus CA|Cronus UK)

This image has an empty alt attribute
Table Mapping Setup

You can customize how individual fields are processed. The following field actions exists:

  • Unfold – Include all fields from related table
  • Unfold DimensionSet – Include all dimension value in the current dimenison Set
  • Exclude – Do not add the field to the cloud table
This image has an empty alt attribute
Field Actions

By opening the Replication Log you can monitor all replication jobs.

This image has an empty alt attribute
Replication Log

Automatic replication is started from the Job Queue by creating a Job Queue with codeunit 70319891.