Mapped vs. replicated schema

Broadly, there are two options for importing customer data depending on the uses for that data.

Import mode	Destination fata format	When to use
Mapped schema	Data queryable in a single schema, with an additional column on each table to indicate data ownership: `organization_id`.	Data needs to conform to a fixed format/schema.
Replicated schema	Data replicated into multiple schemas -- one per tenant -- with the schema name indicating data ownership.	Data can arrive in any shape. Will often require further whiteglove data onboarding.

In **Mapped schema** mode, data arrives in a multi-tenanted table.
In **Replicated schema** mode, an individual schema is created per tenant.

📘
Using Mapped schema mode and configuring data mapping
To use Mapped schema mode, source connections must be submitted with the model_mappings field. This object provides the source-to-destination column mapping required to transform and efficiently transfer the source data.

📘Using Mapped schema mode and configuring data mapping

📘
Using `Mapped schema` mode and configuring data mapping