Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs: data studio updates (#72641)

Alex Yarosh33d9cfb809ed
diff --git a/docs/data-modeling/metadata-editing.md b/docs/data-modeling/metadata-editing.md
index 9c6d7c01509..af4912a4083 100644
--- a/docs/data-modeling/metadata-editing.md
+++ b/docs/data-modeling/metadata-editing.md
@@ -6,7 +6,7 @@ redirect_from:
# Table metadata editing
-> Prefer using [Data Studio > Data structure](../data-studio/data-structure.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase.
+> Prefer using [Data Studio > Tables](../data-studio/managing-tables.md) for metadata editing. The page _Admin > Table Metadata_ will be removed in future versions of Metabase.
_Admin > Table metadata_
diff --git a/docs/data-modeling/metrics.md b/docs/data-modeling/metrics.md
index a8456552757..f8a65afce79 100644
--- a/docs/data-modeling/metrics.md
+++ b/docs/data-modeling/metrics.md
@@ -89,7 +89,7 @@ To edit a metric:
## Explore and compare metrics
-You can explore metrics, break them out by different dimensions, and compare metrics and [measures](../data-studio/data-structure.md#measures) to each other in the [Metrics Explorer](../questions/metrics-explorer.md).
+You can explore metrics, break them out by different dimensions, and compare metrics and [measures](../data-studio/measures.md) to each other in the [Metrics Explorer](../questions/metrics-explorer.md).
![Metrics explorer](./images/metric-explorer.png)
@@ -166,7 +166,7 @@ Prefer using the [Library](../data-studio/library.md#metrics) to let people know
## Further reading
-- [Measures](../data-studio/data-structure.md#measures)
+- [Measures](../data-studio/measures.md)
- [Models](./models.md)
- [Segments](./segments.md)
- [SQL Snippets](../questions/native-editor/snippets.md)
diff --git a/docs/data-modeling/model-persistence.md b/docs/data-modeling/model-persistence.md
index 4415d1bfefb..8060ec7147c 100644
--- a/docs/data-modeling/model-persistence.md
+++ b/docs/data-modeling/model-persistence.md
@@ -4,7 +4,7 @@ title: Model persistence
# Model persistence
-> Prefer [Transforms](../data-studio/transforms/transforms-overview.md) instead of model persistence. Model persistence remains supported for now, but it will be deprecated in future versions of Metabase.
+> Prefer [Transforms](../data-studio/transforms/transforms-overview.md) instead of model persistence. Model persistence remains supported for now, but it will be deprecated in future versions of Metabase. You can [convert models to transforms in bulk](../data-studio/transforms/transforms-overview.md#convert-models-to-transforms).
Metabase can persist the results of your models so that your models (and the questions based on those models) load faster.
diff --git a/docs/data-modeling/models.md b/docs/data-modeling/models.md
index ec7379277d3..ccbdf421ecd 100644
--- a/docs/data-modeling/models.md
+++ b/docs/data-modeling/models.md
@@ -6,7 +6,7 @@ redirect_from:
# Models
-> Consider using [Transforms](../data-studio/transforms/transforms-overview.md) instead of models.
+> Consider using [Transforms](../data-studio/transforms/transforms-overview.md) instead of models. You can [convert models to transforms in bulk](../data-studio/transforms/transforms-overview.md#convert-models-to-transforms).
Models curate data from another table or tables from the same database to anticipate the kinds of questions people will ask of the data. You can think of them as derived tables, or a special kind of saved question meant to be used as the starting point for new questions. You can base a model on a SQL or query builder question, which means you can include custom, calculated columns in your model.
@@ -218,6 +218,14 @@ See [content verification](../exploration-and-organization/content-verification.
See [Model persistence](./model-persistence.md)
+## Convert a model to a transform
+
+[Transforms](../data-studio/transforms/transforms-overview.md) are the successor to models. Transforms create a persistent table in your database that refreshes on a schedule, instead of running the query live each time. Metabase will be gradually phasing out models in favor of transforms.
+
+If you're an admin, you can convert existing models to transforms one at a time. Conversion creates a transform from the model's query, runs it to produce the output table, and then updates all questions and dashboards that used the model to use the transform's table instead. The model itself becomes a saved question.
+
+See [Convert existing models to transforms](../data-studio/transforms/transforms-overview.md#convert-models-to-transforms).
+
## Further reading
- [Models in Metabase][learn-models]
diff --git a/docs/data-modeling/segments.md b/docs/data-modeling/segments.md
index 0b405443f31..88433d8e4d7 100644
--- a/docs/data-modeling/segments.md
+++ b/docs/data-modeling/segments.md
@@ -4,7 +4,7 @@ title: "Segments"
# Segments
-> Prefer [Data Studio](../data-studio/data-structure.md#segments) for managing segments.
+> Prefer [Data Studio](../data-studio/segments.md) for managing segments.
Metabase allows admins to create segments so people can quickly and easily reference them in the query builder.
diff --git a/docs/data-studio/data-structure.md b/docs/data-studio/data-structure.md
deleted file mode 100644
index f270e2a614b..00000000000
--- a/docs/data-studio/data-structure.md
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: Data structure
-summary: See all the tables in your Metabase, edit and sync metadata, edit column types, set visibility, publish tables, and more.
----
-
-# Data structure
-
-_Data studio > Data structure_
-
-![Data structure](./images/data-structure.png)
-
-The **Data structure** area of [Data Studio](overview.md) is where you can manage table metadata to make it easier for people to work with your data.
-
-You can do things like:
-
-- Browse all the tables in your Metabase
-- Publish tables to the Library
-- Sync and scan tables
-- Assign owners and other attributes to tables
-- Set table and field visibility
-- Edit table and column names and types
-- Set data formatting settings
-- Create measures and segments
-
-## Permissions for Data Structure
-
-To access the Data Structure area of Data Studio, you need to be a member of the Admin group or the Data Analyst group (Data Analyst group is only available on Pro/Enterprise plans).
-
-People in the Data Analyst group will have table metadata and data structure access to _all_ tables in your Metabase, even if they have limited View Data permissions for those tables. If you only want to give someone access to table metadata for some - but not all - tables, use the table metadata permissions and access the Table Metadata through Admin > Table metadata instead of Data Studio.
-
-## Browse tables
-
-The Data Structure tab gives you an overview of all tables in all databases connected to your Metabase, together with their owner, row count, and published state. For now, Metabase only displays row counts for PostgreSQL tables.
-
-You can search for table names, but the search will only match beginnings of words in table names. So for example, if you search for “base”, results will include names like “Baseball stats” and “All your base are belong to us”, but the results won't include tables like “Metabase secrets”.
-
-You can also filter tables by attributes like owners, visibility, or source - for example, if you wanted to find all hidden tables, or all tables created from CSV uploads.
-
-You can set [table attributes](#table-attributes), [edit metadata](#table-and-field-metadata), [publish the table](#publishing-and-unpublishing-tables) or create [segments](#segments) or [measures](#measures) on the table. You can also select tables in bulk to publish or assign attributes (including visibility) to multiple tables at once.
-
-## Publishing and unpublishing tables
-
-![Publishing a table from Data structure](./images/data-structure-publish.png)
-
-{% include plans-blockquote.html feature="Publishing tables to the Library" %}
-
-Once you select a table in Data Structure, you can publish the table to add it to the Library. The Library is a special collection that helps you create a source of truth for analytics by providing a centrally managed set of curated content.
-
-See [Publishing tables](./library.md#publishing-tables) in the [Library docs](./library.md).
-
-## Sync settings
-
-You can trigger manual re-sync of the table schema. Re-syncing can be useful if you have added or removed columns from the table, and you don't see those changes reflected in Metabase.
-
-You can also re-scan field values for the table or discard cached field values, which is useful if you need to retrieve updated values for dropdown filters.
-
-See [syncs and scans](../databases/sync-scan.md) for more information.
-
-## Table attributes
-
-### Owner
-
-Table **owner** can be a Metabase user or an arbitrary email address. Use this owner attribute to let people know who on your team is responsible for which table.
-
-Table owner attribute is not exposed to people outside Data Studio.
-
-### Visibility layer
-
-The **Visibility layer** attribute controls whether people in your Metabase can see the table when building new queries. You can also use it to tag tables according to how ready for end-user consumption they are (for example, if you're using medallion architecture).
-
-The options are:
-
-- **Hidden**: the table isn't available in the query builder and isn't [synced](../databases/sync-scan.md). People with SQL access can still query the table.
-- **Internal**: table visible in the query builder and synced.
-- **Final**: table is visible in the query builder and synced.
-
-Table visibility layer can be used as a tool to improve user experience of people working in your Metabase, and it should _not be used to control access_ - use [data permissions](../permissions/data.md) to control access instead.
-
-### Entity type
-
-You can use **entity type** to tell people what kind of information is contained in the table, for example "Transaction" or "Event". Metabase will try to detect and automatically assign appropriate entity types (like entity type "Person" for a `Users` table"), but you can always change it later.
-
-Outside Data Studio, entity type determines the record icons in the [details view](../exploration-and-organization/exploration.md#view-details-of-a-record).
-
-### Source
-
-**Source** describes where the data comes from. It can be useful when you want to identify tables that are, for example, ingested tables, or tables coming from CSV uploads.
-
-Metabase will automatically assign the source "Metabase transforms” to tables created by [Metabase transforms](./transforms/transforms-overview.md), and source "Uploaded data" to tables created by new [CSV uploads](../databases/uploads.md) (CSV uploads that you created before getting Data Studio will not be automatically tagged).
-
-## Table and field metadata
-
-You can edit field descriptions, types, visibility settings, and formatting. For example, you can choose to display a filter on a field as a dropdown, or display days as `21.03.2026` instead of `03/21/2026`.
-
-See [Table metadata editing](../data-modeling/metadata-editing.md).
-
-## Segments
-
-Segments are saved filters on tables. You can use segments to create an official definition of a subset of customers, users, or products that everyone on your team can refer to consistently (for example what constitutes an "active user").
-
-People will see segments as options in the Filter block of the [query builder](../questions/query-builder/editor.md).
-
-For now, in addition to Data Studio, segments can also be managed through **Admin > Table Metadata**, see [Segments in table metadata](../data-modeling/segments.md).
-
-To see all segments on a table, select the table in **Data Structure** and switch to **Segments** tab.
-
-### Create a segment
-
-1. Select the table in **Data structure**.
-2. Scroll down and switch to **Segments**.
-3. Click on **+New Segment**. You'll see an abridged version of Metabase's query builder.
-4. Add the filters describing the segment (e.g. `Active = true`) and name the segment.
-5. To preview the records in the segment, click on the **three dots** icon next to the segment's name and select **Preview**.
-6. Save.
-
-### Use a segment in the query builder
-
-To use a segment in the query builder, start a new question from the table that the segment is based on, and select the segment in the **Filter** block. The segment's filters will be applied behind the scenes.
-
-### Delete a segment
-
-Deleting a segment will not break questions using it. The questions that use the segment will keep using the same filters as before.
-
-1. Select the table in **Data structure**.
-2. Scroll down and switch to **Segments** and choose your segment.
-3. On the segment's page, click on the **three dots** icon next to the segment's name and select **Remove segment**.
-
-## Measures
-
-Measures are saved aggregations on tables. You can use measures to create an official saved calculation, like what "Net Promoter Score" is calculated.
-
-People will see measures as options in the Summarize block of the [query builder](../questions/query-builder/editor.md).
-
-To see all measures on a table, select the table in **Data structure** and switch to **Measures** tab.
-
-### Create a measure
-
-1. Select the table in **Data structure**.
-2. Scroll down and switch to **Measures**.
-3. Click on **+New measure**. You'll see an abridged version of Metabase's query builder that focuses on aggregation.
-4. Add your aggregation. For more complex aggregations, check out [custom expressions](../questions/query-builder/expressions.md).
-5. To preview the results of the measure, click on the **three dots** icon next to the measure's name and select **Preview**.
-
-### Use a measure in the query builder
-
-To use a measure in the query builder, start a new question from the table that the measure is based on, and select the measure in the **Summarize** block. The measure's saved aggregation will be applied behind the scenes. You can use breakouts with a saved measure.
-
-### Delete a measure
-
-Deleting a measure will not break questions using it. The questions that use the measure will keep using the same aggregations as before.
-
-1. Select the table in **Data structure**.
-2. Scroll down and switch to **Measures** and choose your measure.
-3. On the measure's page, click on the **three dots** icon next to the measure's name and select **Remove measure**.
-
-### Explore a measure
-
-You can explore measures along dimensions and compare measures and measures in the [Metrics Explorer](../questions/metrics-explorer.md).
diff --git a/docs/data-studio/dependency-diagnostics.md b/docs/data-studio/dependencies/diagnostics.md
similarity index 82%
rename from docs/data-studio/dependency-diagnostics.md
rename to docs/data-studio/dependencies/diagnostics.md
index 0fc23f9b5a3..fd2aa0b9bda 100644
--- a/docs/data-studio/dependency-diagnostics.md
+++ b/docs/data-studio/dependencies/diagnostics.md
@@ -1,6 +1,8 @@
---
title: Dependency diagnostics
summary: Find broken content and unused items so you can fix problems and clean up safely.
+redirect_from:
+ - /docs/latest/data-studio/dependency-diagnostics
---
# Dependency diagnostics
@@ -11,24 +13,22 @@ Dependency diagnostics shows you content with broken dependencies, and content t
To open Dependency diagnostics:
-1. Open [Data Studio](./overview.md).
+1. Open [Data Studio](../overview.md).
2. Click **Dependency diagnostics** in the left sidebar.
Dependency diagnostics has two tabs: **Broken dependencies** and **Unreferenced entities**.
## Broken dependencies
-![Broken dependencies](./images/broken-dependencies.png)
+![Broken dependencies](../images/broken-dependencies.png)
-> Note: Broken dependency detection currently covers only questions built with the query builder (MBQL). SQL questions and SQL models aren't included.
-
-Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../data-modeling/metadata-editing.md).
+Broken dependencies lists items that other content depends on, where a dependent item references a column or field the item no longer provides. This can happen when a column is removed or renamed, or when a field is hidden from the query builder by setting Visibility to **Do not include** in [metadata editing](../../data-modeling/metadata-editing.md).
The broken dependencies table includes:
- Tables
-- [Questions](../questions/introduction.md)
-- [Models](../data-modeling/models.md)
+- [Questions](../../questions/introduction.md)
+- [Models](../../data-modeling/models.md)
For each item, the list shows:
@@ -46,7 +46,7 @@ Selecting an item opens a details panel with:
- The item's name, owner, and creation date
- A list of missing or invalid columns, with copy buttons to help fix references
- Downstream items that are broken because of this specific issue. You can filter this list by entity type
-- Quick links to open items or view them in the [dependency graph](./dependency-graph.md)
+- Quick links to open items or view them in the [dependency graph](./graph.md)
For tables created by transforms, the sidebar also shows a link to the source transform.
@@ -70,23 +70,23 @@ To fix this, either restore the expected column names in the SQL query or update
## Unreferenced entities
-![Unreferenced entities](./images/unreferenced-entities.png)
+![Unreferenced entities](../images/unreferenced-entities.png)
Unreferenced entities shows items that aren't used by any other non-archived content. Use this view to clean up unused content, especially reusable items like measures, metrics, and snippets. Start by checking why an item was created, when it was last edited, and whether it was meant to be reused.
-An unreferenced item isn't broken and isn't automatically safe to delete. It simply means nothing else depends on it. Check [Usage analytics](../usage-and-performance-tools/usage-analytics.md) for view activity before you archive or delete an item.
+An unreferenced item isn't broken and isn't automatically safe to delete. It simply means nothing else depends on it. Check [Usage analytics](../../usage-and-performance-tools/usage-analytics.md) for view activity before you archive or delete an item.
-The Unreferenced entities list is limited to what you can access, so an item can show up as unreferenced even if something you can’t see depends on it.
+The Unreferenced entities list is limited to what you can access, so an item can show up as unreferenced even if something you can't see depends on it.
Unreferenced entities includes:
- Tables
-- [Questions](../questions/introduction.md)
-- [Models](../data-modeling/models.md)
-- [Metrics](../data-modeling/metrics.md)
+- [Questions](../../questions/introduction.md)
+- [Models](../../data-modeling/models.md)
+- [Metrics](../../data-modeling/metrics.md)
- Segments
- Measures
-- [Snippets](../questions/native-editor/snippets.md)
+- [Snippets](../../questions/native-editor/snippets.md)
For each item, the list shows:
@@ -99,6 +99,6 @@ Selecting an item opens a details panel with:
- Who created the item and when
- When it was last edited
-- Links to open the item or view it in the [dependency graph](./dependency-graph.md)
+- Links to open the item or view it in the [dependency graph](./graph.md)
For tables, the sidebar also shows owners, descriptions, and links to open the schema or database. For tables created by transforms, the sidebar shows a link to the source transform.
diff --git a/docs/data-studio/dependency-graph.md b/docs/data-studio/dependencies/graph.md
similarity index 74%
rename from docs/data-studio/dependency-graph.md
rename to docs/data-studio/dependencies/graph.md
index 608a04d04ba..85893fd7942 100644
--- a/docs/data-studio/dependency-graph.md
+++ b/docs/data-studio/dependencies/graph.md
@@ -1,13 +1,15 @@
---
title: Dependency graph
summary: Visualize how your content connects and what depends on what in Metabase.
+redirect_from:
+ - /docs/latest/data-studio/dependency-graph
---
# Dependency graph
{% include plans-blockquote.html feature="Dependency graph" %}
-![Dependency graph](./images/dependency-graph.png)
+![Dependency graph](../images/dependency-graph.png)
The dependency graph provides a visual representation of how your Metabase content is connected. You can use it to follow how data flows through your Metabase to better understand the impact of any changes you make.
@@ -16,19 +18,19 @@ The dependency graph provides a visual representation of how your Metabase conte
The dependency graph tracks the relationships between:
- Tables
-- [Questions](../questions/introduction.md)
-- [Models](../data-modeling/models.md)
-- [Snippets](../questions/native-editor/snippets.md)
-- [Transforms](./transforms/transforms-overview.md)
-- [Metrics](../data-modeling/metrics.md)
-- [Dashboards](../dashboards/introduction.md)
-- [Documents](../documents/introduction.md)
+- [Questions](../../questions/introduction.md)
+- [Models](../../data-modeling/models.md)
+- [Snippets](../../questions/native-editor/snippets.md)
+- [Transforms](../transforms/transforms-overview.md)
+- [Metrics](../../data-modeling/metrics.md)
+- [Dashboards](../../dashboards/introduction.md)
+- [Documents](../../documents/introduction.md)
## Viewing the dependency graph
To open the full dependency graph:
-1. Open [Data Studio](./overview.md).
+1. Open [Data Studio](../overview.md).
2. Click **Dependency graph** in the left sidebar.
This opens a canvas view where you can search for and visualize the dependencies of any item across your entire Metabase instance.
@@ -62,11 +64,16 @@ Because of this, dependencies can exist even when no data is directly queried. F
- A question used only to populate a dashboard filter dropdown still counts as a dependency
- Questions that are joined together may appear as separate dependent items
-Some dependencies are inferred rather than explicitly defined. SQL queries can introduce implicit joins, and complex questions may have multiple internal dependency paths instead of a single source to result flow. As a result, a dependency may appear in the graph even if it’s not obvious from the question editor.
+Some dependencies are inferred rather than explicitly defined. SQL queries can introduce implicit joins, and complex questions may have multiple internal dependency paths instead of a single source to result flow. As a result, a dependency may appear in the graph even if it's not obvious from the question editor.
If a dependency looks unexpected, it usually reflects an indirect or inferred relationship. In those cases, review how the item is used before changing or removing it.
+## Replace data sources
+
+You can use the dependency graph to replace query sources in bulk. See [Replace data sources](replace-data-sources.md).
+
## Further reading
-- [Library](./library.md)
-- [Dependency graph](./dependency-graph.md)
+- [Library](../library.md)
+- [Dependency diagnostics](./diagnostics.md)
+- [Replace data sources](./replace-data-sources.md)
diff --git a/docs/data-studio/dependencies/replace-data-sources.md b/docs/data-studio/dependencies/replace-data-sources.md
new file mode 100644
index 00000000000..b8f6675c782
--- /dev/null
+++ b/docs/data-studio/dependencies/replace-data-sources.md
@@ -0,0 +1,143 @@
+---
+title: Replace data sources
+summary: Admins can swap out a table, model, or question and replace it with a different one across your entire Metabase.
+---
+
+# Replace data sources
+
+{% include plans-blockquote.html feature="Replacing data sources" %}
+
+Admins can swap out a table, model, or question and replace it with a different one across your entire Metabase.
+
+For example, let's say you created a transform that created a cleaned up version of your `orders` table, called `orders_clean`. Instead of rewriting all your questions that query the `orders` table, Admins can swap in the `order_clean` table everywhere the old `orders` table is referenced.
+
+## How replacing data sources works
+
+- Only admins can replace data sources.
+
+- Metabase uses the [dependency graph](./graph.md) to identify all content that depends on the original data source. "Data source" here could be a table, model, or question queried by another entity.
+
+- Once an admin [selects a replacement source](#find-and-replace-data-sources), Metabase [checks compatibility](#compatibility-requirements) of the original data source with the replacement data source.
+
+- If data sources are compatible, Metabase walks through the entire dependency graph for the original data source and changes all queries to use the new data source instead. Metabase only swaps data sources where they're used specifically as _data sources_ for queries - and not, for example, lists of values or custom destinations, see [What gets replaced](#what-gets-replaced).
+
+- The original data source is _not deleted_ after the replacement is finished.
+
+## Compatibility requirements
+
+You can replace a table, model, or saved question with any other table, model, or saved question, as long as the two sources satisfy the following requirements:
+
+### General requirements
+
+- **Original and new data sources must be in the same database**.
+
+ For questions/models, this means that the underlying tables must be in the same database.
+
+- **Original data source isn't used in any [row or column security policies](../../permissions/row-and-column-security.md)**.
+
+ This is necessary to avoid accidentally exposing any data after the replacement is finished.
+
+- **New data source can't depend on the original data source**.
+
+ For example, you can't replace a table with a model based on the same table, or with an output of a transform built on the same table.
+
+### Column requirements
+
+- **All columns from the original source must be in the new data source.**
+
+ Columns are matched by their database name (not their display name). New data source can have more columns than the original data source, but it can't have fewer columns.
+
+- **Column types must match**.
+
+ This means that, for example, if the column `user_id` is an integer in the old data source, it also must be an integer (and not a string or UUID) in the new data source.
+
+- **If the original column is a Metabase _foreign_ key, the replacement column must be too.**
+
+ For example, if `old_table` has `User ID` column with Metabase semantic type "Foreign key" to the `ID` column of `users` table, then the replacement source `new_table` also must have a `User ID` column with Metabase foreign key to `ID` from `users`.
+
+ Only foreign keys defined in Metabase need to match. Database-defined foreign keys aren't checked.
+
+- **If the original column is a Metabase _entity_ key, the replacement column must be too.**
+
+ For example, if `old_table` has `ID` column with Metabase semantic type "Entity key", then the replacement source `new_table` also must have an `ID` column with Metabase semantic type "Entity key".
+
+- If replacing a table, that **original table can't be a target of a Metabase's [semantic foreign keys](../../data-modeling/semantic-types.md)** from other tables.
+
+ Foreign keys can still exist on the database level, but not on the level of Metabase semantic types. This requirement is necessary to avoid issues with implicit joins when swapping tables.
+
+ The old table can still have foreign keys _to_ other tables, it just can't be the _target_ of a foreign key.
+
+## Find and replace data sources
+
+{% include plans-blockquote.html feature="Dependency graph" %}
+
+Only admins can replace data sources.
+
+To find and replace all entities that depend on a data source:
+
+1. Go to **Data Studio** by clicking the **grid icon** in the top right and selecting **Data Studio**;
+2. In Data Studio, click **Dependency graph** in the sidebar and search for the table, model, or question you want to replace.
+3. Click the card for the data source and in the info panel on the right, click the **Find and replace** icon.
+ ![Find and replace](../images/find-and-replace.png)
+4. In the left sidebar, select replacement data source.
+5. If Metabase can't go ahead with replacement, you'll see error messages next to data sources, and [compatibility requirements](#compatibility-requirements) errors in the "Column comparison table".
+
+ ![Compatibility requirements](../images/compatibility-requirements.png)
+
+6. If the sources are compatible, you can check out the list of items that will be changed:
+
+ ![Preview changes](../images/check-repalce-changes.png)
+
+7. Once you verified the changes, click "Replace data source" in the bottom of the left sidebar.
+
+### Running the replacement
+
+If your Metabase has thousands of questions, replacement can take a long time (potentially hours).
+
+Metabase runs the replacement asynchronously in the background. A status indicator appears at the bottom of the screen showing progress and completion. When complete, all affected items are updated to use the new data source.
+
+If the replacement fails partway through, some items may already be updated. Check the status indicator for details.
+
+You can cancel a replacement while it's running. Items that were already updated before you canceled won't be reverted.
+
+Only one replacement can run at any time.
+
+## What gets replaced
+
+Items are replaced when (and only when) they are used as a query source. This includes:
+
+- Data sources (including in joins) in questions, models, and metrics built with the query builder
+- Data sources for measures and segments
+- Tables in `FROM` statements in SQL queries
+- [Questions and models referenced from SQL questions](../../questions/native-editor/referencing-saved-questions-in-queries.md)
+- Field filters
+
+Metabase **will not replace** tables/models/questions in:
+
+- Snippets
+- Questions or models that power dropdown filter values in SQL questions and dashboards
+- [Links](../../dashboards/introduction.md#link-cards) and [custom destinations](../../dashboards/interactive.md#custom-destinations) on dashboards;
+- Targets for [actions](../../actions/introduction.md).
+
+Metabase will **not allow** you to replace data sources that are used as:
+
+- Row or column security policies
+- Targets of foreign keys
+
+## Permissions and data source replacement
+
+Metabase **won't check** whether swapped data sources have comparable permissions. Admins need to make sure that new data source has appropriate permissions _before_ initiating the replacement, otherwise you could block people from viewing questions, or expose data they're not supposed to see.
+
+For example, the Customer group might have view data access to `old_table`, but have blocked (no) access to `new_table`. If you replace `old_table` with `new_table`, then people in the Customers group won't be able to see results in questions that used to query the `old_table` and now query the blocked `new_table`.
+
+Review both data and collection permissions for old and new sources before starting replacement.
+
+## Avoid using data source replacement with remote sync enabled
+
+Because old data sources can be used both in synced and unsynced collections, we do not recommend swapping data sources in bulk when remote sync is enabled.
+
+## Limitations
+
+- The source and target must be on the same database. Cross-database replacement isn't supported.
+- Original and new data source have to satisfy [compatibility requirements](#compatibility-requirements).
+- All uses of the original data source is swapped for the new data source. You can't pick and choose which content to update.
diff --git a/docs/data-studio/images/check-repalce-changes.png b/docs/data-studio/images/check-repalce-changes.png
new file mode 100644
index 00000000000..76f5f821adf
Binary files /dev/null and b/docs/data-studio/images/check-repalce-changes.png differ
diff --git a/docs/data-studio/images/compatibility-requirements.png b/docs/data-studio/images/compatibility-requirements.png
new file mode 100644
index 00000000000..d37486f40d8
Binary files /dev/null and b/docs/data-studio/images/compatibility-requirements.png differ
diff --git a/docs/data-studio/images/explore-measure.png b/docs/data-studio/images/explore-measure.png
new file mode 100644
index 00000000000..17a10ba2194
Binary files /dev/null and b/docs/data-studio/images/explore-measure.png differ
diff --git a/docs/data-studio/images/find-and-replace.png b/docs/data-studio/images/find-and-replace.png
new file mode 100644
index 00000000000..2ea75e3a7a2
Binary files /dev/null and b/docs/data-studio/images/find-and-replace.png differ
diff --git a/docs/data-studio/images/find-measures.png b/docs/data-studio/images/find-measures.png
new file mode 100644
index 00000000000..afebe954a9d
Binary files /dev/null and b/docs/data-studio/images/find-measures.png differ
diff --git a/docs/data-studio/images/measure-definition.png b/docs/data-studio/images/measure-definition.png
new file mode 100644
index 00000000000..2191d6be91a
Binary files /dev/null and b/docs/data-studio/images/measure-definition.png differ
diff --git a/docs/data-studio/images/measure.png b/docs/data-studio/images/measure.png
new file mode 100644
index 00000000000..19d5cd6e1b0
Binary files /dev/null and b/docs/data-studio/images/measure.png differ
diff --git a/docs/data-studio/images/segment-definition.png b/docs/data-studio/images/segment-definition.png
new file mode 100644
index 00000000000..d3cf5861087
Binary files /dev/null and b/docs/data-studio/images/segment-definition.png differ
diff --git a/docs/data-studio/images/segment.png b/docs/data-studio/images/segment.png
new file mode 100644
index 00000000000..39ec8d5bf1e
Binary files /dev/null and b/docs/data-studio/images/segment.png differ
diff --git a/docs/data-studio/library.md b/docs/data-studio/library.md
index 773e479a8c1..452593e30be 100644
--- a/docs/data-studio/library.md
+++ b/docs/data-studio/library.md
@@ -51,7 +51,7 @@ Once a table is published, you can view and manage its metadata, and more.
- Fields
- [Segments](../data-modeling/segments.md)
- Measures
-- [Dependencies](./dependency-graph.md)
+- [Dependencies](./dependencies/graph.md)
To query a table from the Library in Data Studio:
@@ -99,7 +99,7 @@ Metabase uses the standard [collection permissions](../permissions/collections.m
## Further reading
-- [Dependency graph](./dependency-graph.md)
+- [Dependency graph](./dependencies/graph.md)
- [Remote sync](../installation-and-operation/remote-sync.md)
- [Models](../data-modeling/models.md)
- [Metrics](../data-modeling/metrics.md)
diff --git a/docs/data-studio/managing-tables.md b/docs/data-studio/managing-tables.md
new file mode 100644
index 00000000000..9192ad221b4
--- /dev/null
+++ b/docs/data-studio/managing-tables.md
@@ -0,0 +1,127 @@
+---
+title: Managing tables
+summary: See all the tables in your Metabase, edit and sync metadata, edit column types, set visibility, publish tables, and more.
+redirect_from:
+ - /docs/latest/data-studio/data-structure
+---
+
+# Managing tables
+
+_Data Studio > Tables_
+
+![Data structure](./images/data-structure.png)
+
+You can manage table settings metadata to make it easier for people to work with your data in **Data Studio > Tables**.
+
+You can do things like:
+
+- Browse all the tables in your Metabase
+- Publish tables to the Library
+- Sync and scan tables
+- Assign owners and other attributes to tables
+- Set table and field visibility
+- Edit table and column names and types
+- Set data formatting settings
+- Create measures and segments
+
+## Permissions for managing tables in Data Studio
+
+To access the Tables area of Data Studio, you need to be a member of the Admin group or the Data Analyst group (Data Analyst group is only available on Pro/Enterprise plans).
+
+People in the Data Analyst group will have table metadata and data structure access to _all_ tables in your Metabase, even if they have limited View Data permissions for those tables. If you only want to give someone access to table metadata for some - but not all - tables, use the table metadata permissions and access the Table Metadata through Admin > Table metadata instead of Data Studio.
+
+## Browse tables
+
+_Data Studio > Tables_
+
+You can see all tables in all databases connected to your Metabase in **Data Studio > Tables**, together with their owner, row count, and published state. For now, Metabase only displays row counts for PostgreSQL tables.
+
+You can search for table names, but the search will only match beginnings of words in table names. So for example, if you search for "base", results will include names like "Baseball stats" and "All your base are belong to us", but the results won't include tables like "Metabase secrets".
+
+You can also filter tables by attributes like owners, visibility, or source - for example, if you wanted to find all hidden tables, or all tables created from CSV uploads.
+
+You can set [table attributes](#table-attributes), [edit metadata](#table-and-field-metadata), [publish the table](#publishing-and-unpublishing-tables) or create [segments](./segments.md) or [measures](./measures.md) on the table. You can also select tables in bulk to publish or assign attributes (including visibility) to multiple tables at once.
+
+## Publishing and unpublishing tables
+
+_Data Studio > Tables > Details_
+
+![Publishing a table from Data structure](./images/data-structure-publish.png)
+
+{% include plans-blockquote.html feature="Publishing tables to the Library" %}
+
+Once you select a table in **Data Studio > Tables**, you can publish the table to add it to the Library. The Library is a special collection that helps you create a source of truth for analytics by providing a centrally managed set of curated content.
+
+See [Publishing tables](./library.md#publishing-tables) in the [Library docs](./library.md).
+
+## Find and replace tables
+
+You can replace every occurrence of a table as a data source with another table. See [Replace data sources](./dependencies/replace-data-sources.md).
+
+## Sync settings
+
+_Data Studio > Tables > Details_
+
+You can trigger manual re-sync of the table schema in **Data Studio > Tables** in the **Details** tab. Re-syncing can be useful if you have added or removed columns from the table, and you don't see those changes reflected in Metabase.
+
+You can also re-scan field values for the table or discard cached field values, which is useful if you need to retrieve updated values for dropdown filters.
+
+See [syncs and scans](../databases/sync-scan.md) for more information.
+
+## Table attributes
+
+_Data Studio > Tables > Details_
+
+You can configure table attributes in **Data Studio > Tables** in the **Details** tab.
+
+### Owner
+
+Table **owner** can be a Metabase user or an arbitrary email address. Use this owner attribute to let people know who on your team is responsible for which table.
+
+Table owner attribute is not exposed to people outside Data Studio.
+
+### Visibility layer
+
+The **Visibility layer** attribute controls whether people in your Metabase can see the table when building new queries. You can also use it to tag tables according to how ready for end-user consumption they are (for example, if you're using medallion architecture).
+
+The options are:
+
+- **Hidden**: the table isn't available in the query builder and isn't [synced](../databases/sync-scan.md). People with SQL access can still query the table.
+- **Internal**: table visible in the query builder and synced.
+- **Final**: table is visible in the query builder and synced.
+
+Table visibility layer can be used as a tool to improve user experience of people working in your Metabase, and it should _not be used to control access_ - use [data permissions](../permissions/data.md) to control access instead.
+
+### Entity type
+
+You can use **entity type** to tell people what kind of information is contained in the table, for example "Transaction" or "Event". Metabase will try to detect and automatically assign appropriate entity types (like entity type "Person" for a `Users` table"), but you can always change it later.
+
+Outside Data Studio, entity type determines the record icons in the [details view](../exploration-and-organization/exploration.md#view-details-of-a-record).
+
+### Source
+
+**Source** describes where the data comes from. It can be useful when you want to identify tables that are, for example, ingested tables, or tables coming from CSV uploads.
+
+Metabase will automatically assign the source "Metabase transforms" to tables created by [Metabase transforms](./transforms/transforms-overview.md), and source "Uploaded data" to tables created by new [CSV uploads](../databases/uploads.md) (CSV uploads that you created before getting Data Studio will not be automatically tagged).
+
+## Table and field metadata
+
+_Data Studio > Tables > Fields_
+
+You can edit field descriptions, types, visibility settings, and formatting. For example, you can choose to display a filter on a field as a dropdown, or display days as `21.03.2026` instead of `03/21/2026`.
+
+See [Table metadata editing](../data-modeling/metadata-editing.md).
+
+## Segments
+
+Segments are saved filters on a table that people can use in the query builder. See [Segments](./segments.md).
+
+## Measures
+
+Measures are saved aggregations on a table that people can use in the query builder. See [Measures](./measures.md).
+
+## Further reading
+
+- [Table metadata editing](../data-modeling/metadata-editing.md)
+- [Segments](./segments.md)
+- [Measures](./measures.md)
diff --git a/docs/data-studio/measures.md b/docs/data-studio/measures.md
new file mode 100644
index 00000000000..a8cb93ae570
--- /dev/null
+++ b/docs/data-studio/measures.md
@@ -0,0 +1,104 @@
+---
+title: Measures
+summary: Create saved aggregations on tables so people can use consistent calculations when building queries.
+---
+
+# Measures
+
+Measures are saved aggregations associated with a table. You can use measures to create an official definition of a calculation—like Net Promoter Score—so everyone in your Metabase uses the same formula instead of writing their own versions.
+
+People will see measures as options in the Summarize block of the [query builder](../questions/query-builder/editor.md).
+
+![Measure in the query builder](./images/measure.png)
+
+## Create measures
+
+> If your instance is in read-only [remote sync](../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create measures on tables published in the Library while in read-only mode.
+
+Measures are created in [Data Studio](../data-studio/overview.md).
+
+1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.
+2. In Data Studio, go to **Tables** in the left sidebar, and select the table to define a measure on.
+3. In the right sidebar for the table, select **Measures**.
+
+ ![Find measures](./images/find-measures.png)
+
+4. Click **+New measure**. You'll see an abridged version of Metabase's query builder that focuses on aggregation.
+
+5. Add your aggregation formula. For more complex aggregations, check out [custom expressions](../questions/query-builder/expressions.md).
+
+ For example, you can define a measure like `(CountIf([Score] >= 9) - CountIf([Score] <= 6)) / Count() * 100` to calculate Net Promoter Score.
+
+ ![Measure definition](./images/measure-definition.png)
+
+6. To preview the results of the measure, click on the **three dots** icon next to the measure's name and select **Preview**.
+7. Save.
+
+## Use measures in the query builder
+
+Measures allow people to use pre-defined aggregations to summarize their data.
+
+To use a measure in the query builder:
+
+1. Start a new question from the table that the measure is based on.
+2. Select the measure in the **Summarize** block.
+
+The measure's saved aggregation will be applied behind the scenes. You can use breakouts with a saved measure.
+
+![Measure in the query builder](./images/measure.png)
+
+Measures are only available to questions that directly query the measure's table. Measures aren't available for questions that join the measure's table, or that involve nested queries (even if those queries measure's table as a source themselves).
+
+## Delete measures
+
+Deleting a measure won't break questions using it. The questions that use the deleted measure will "revert" to using the measure's (now unnamed) aggregation formula.
+
+1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.
+2. In Data Studio, go to **Tables**, and select the measure's table.
+3. In the right sidebar for the table, select **Measures**.
+4. Choose the measure you want to delete.
+5. On the measure's page, click on the **three dots** icon next to the measure's name and select **Remove measure**.
+
+## Explore measures
+
+You can explore measures along dimensions and compare several measures in the [Metrics Explorer](../questions/metrics-explorer.md).
+
+![Explore a measure](./images/explore-measure.png)
+
+To see all measures on a table, select the table in [Data Studio > Managing tables](./managing-tables.md) and switch to the **Measures** tab.
+
+## Permissions for measures
+
+To **create, edit, or delete** measures, people need to:
+
+- Be admins or members of the [Data Analysts](../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.
+- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the measure's table. This is needed to create the measure's query.
+
+To **use** a measure, people need to:
+
+- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the measure's table.
+
+## Only measures on published tables are synced to Git
+
+When using [Remote Sync](../installation-and-operation/remote-sync.md):
+
+- Measures on tables that are _not_ published to the [Library](./library.md) are _not_ synced;
+- Measures on published tables are only synced if [_Library sync is enabled_](./library.md#versioning-the-library).
+
+If your instance is in read-only Remote Sync mode, and the Library sync is enabled, you won't be able to create measures on published tables.
+
+You can, however, sync [Metrics](../data-modeling/metrics.md) on any tables by syncing their collection.
+
+## Limitations
+
+- Measures are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../questions/native-editor/snippets.md).
+- Measures are only available on questions that use the measure's table as the primary data source.
+- All admins and people in the Data Analyst group can create measures on tables they have permissions to query. There aren't additional controls to restrict who can create measures beyond special groups and data permissions.
+- [Only measures on published tables are synced to Git](#only-measures-on-published-tables-are-synced-to-git).
+
+## Further reading
+
+- [Library](./library.md)
+- [Segments](./segments.md)
+- [Metrics](../data-modeling/metrics.md)
+- [SQL snippets](../questions/native-editor/snippets.md)
diff --git a/docs/data-studio/overview.md b/docs/data-studio/overview.md
index 16add161bc3..99b771c201a 100644
--- a/docs/data-studio/overview.md
+++ b/docs/data-studio/overview.md
@@ -18,18 +18,24 @@ Data Studio provides tools to shape and track your data so everyone can trust th
## What's in Data Studio
- **[Library](./library.md)**\*: A curated space for your organization's most trusted analytics content—tables, metrics, and SQL snippets that your data team recommends.
-- **[Data structure](./data-structure.md)**: Add table metadata to make tables easier to work with.
+- **[Managing tables](./managing-tables.md)**: Add table metadata to make tables easier to work with.
+- **[Segments](./segments.md)**: Create saved filters on tables so people can use consistent definitions when building queries.
+- **[Measures](./measures.md)**: Create saved aggregations on tables so people can use consistent calculations when building queries.
- **[Glossary](../exploration-and-organization/data-model-reference.md#glossary)**: Define terms relevant to your business, both for people and agents trying to understand your data.
-- **[Dependency graph](./dependency-graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them.
-- **[Dependency diagnostics](./dependency-diagnostics.md)**\*: See which items have broken dependencies, or that aren't used.
-- **[Transforms](./transforms/transforms-overview.md)**: Wrangle your data in Metabase, write the query results back to your database, and reuse them in Metabase as sources for new queries. Transforms are optional—Metabase queries your connected databases directly without them.
+- **[Dependency graph](./dependencies/graph.md)**\*: A visual map of how your content connects, so you can understand the impact of changes before you make them.
+- **[Dependency diagnostics](./dependencies/diagnostics.md)**\*: See which items have broken dependencies, or that aren't used.
+- **[Replace data sources](./dependencies/replace-data-sources.md)**\*: Swap out a table or model across all content that uses it, in one operation.
+- **[Transforms](./transforms/transforms-overview.md)**: Wrangle your data in Metabase, write the query results back to your database, and reuse them in Metabase as sources for new queries.
\* Available on [Pro and Enterprise plans](https://www.metabase.com/pricing/).
-## Get to Data Studio
+## Permissions for Data Studio
The keys to Data Studio are granted only to people in either the Admin or [Data Analysts](../people-and-groups/managing.md#data-analysts) groups.
+There are additional permissions required to run transforms, see [Permissions for transforms](./transforms/transforms-overview.md#permissions-for-transforms).
+
+## Get to Data Studio
+
1. Click the **grid** icon in the upper right.
2. Select **Data Studio**.
-
diff --git a/docs/data-studio/segments.md b/docs/data-studio/segments.md
new file mode 100644
index 00000000000..70d6e3be26d
--- /dev/null
+++ b/docs/data-studio/segments.md
@@ -0,0 +1,87 @@
+---
+title: Segments
+summary: Create saved filters on tables so people can use consistent definitions when building queries.
+---
+
+# Segments
+
+Segments are saved filters on tables. You can use segments to create official definitions of a subset of customers, users, or products that everyone on your team can refer to consistently (for example what constitutes an "active user").
+
+People will see segments as options in the Filter block of the [query builder](../questions/query-builder/editor.md).
+
+![Segment in the query builder](./images/segment.png)
+
+For now, in addition to Data Studio, segments can also be managed through **Admin > Table Metadata**, see [Segments in table metadata](../data-modeling/segments.md).
+
+To see all segments on a table, select the table in [Managing tables](./managing-tables.md) and switch to the **Segments** tab.
+
+## Create segments
+
+> If your instance is in read-only [remote sync](../installation-and-operation/remote-sync.md) mode, and you enabled sync of the [Library](./library.md), you will not be able to create segments on tables published in the Library while in read-only mode.
+
+Segments are created in [Data Studio](../data-studio/overview.md).
+
+1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.
+2. In Data Studio, go to **Tables** in the left sidebar, and select the table to define a segment on.
+3. In the right sidebar for the table, select **Segments**.
+4. Click on **+ New Segment**. You'll see an abridged version of Metabase's query builder.
+5. Add the filters describing the segment (e.g. `Active = true`) and name the segment.
+
+ ![Segment definition](./images/segment-definition.png)
+
+6. To preview the records in the segment, click on the **three dots** icon next to the segment's name and select **Preview**.
+7. Save.
+
+## Use segments in the query builder
+
+Segments allow people to use pre-defined filters for their data.
+
+To use a segment in the query builder:
+
+1. Start a new question from the table that the segment is based on.
+2. Select the segment in the **Filter** block. The segment's filters will be applied behind the scenes.
+
+Segments will only appear in questions that use the segment's table as the primary data source. They will not appear in questions joining the segment's table, or in questions built on other questions or models, even if those questions or models use the segment's table as a source themselves.
+
+## Delete segments
+
+Deleting a segment will not break questions using it. The questions that use the segment will keep using the same filters as before.
+
+1. Go to **Data Studio** by clicking the **grid icon** in top right of the screen and selecting **Data Studio**.
+2. In Data Studio, go to **Tables**, and select the segment's table.
+3. In the right sidebar for the table, switch to **Segments** tab
+4. Choose the segment you want to delete.
+5. On the segment's page, click on the **three dots** icon next to the segment's name and select **Remove segment**.
+
+## Permissions for segments
+
+To **create, edit, or delete** segments, people need to:
+
+- Be admins or members of the [Data Analysts](../people-and-groups/managing.md#data-analysts) group. This is needed to access Data Studio.
+- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the segment's table. This is needed to create the segment's query.
+
+To **use** a segment, people need to:
+
+- Have [Create queries](../permissions/data.md#create-queries-permissions) permissions on the segment's table.
+
+## Only segments on published tables are synced to Git
+
+When using [Remote Sync](../installation-and-operation/remote-sync.md):
+
+- Segments on tables that are _not_ published to the [Library](./library.md) are _not_ synced;
+- Segments on published tables are only synced if [_Library sync is enabled_](./library.md#versioning-the-library).
+
+If your instance is in read-only Remote Sync mode, and the Library sync is enabled, you won't be able to create segments on published tables.
+
+## Limitations
+
+- Segments are only available for use in the query builder. For defining reusable bits of SQL, check out [Snippets](../questions/native-editor/snippets.md).
+- Segments are only available on questions that use the segment's table as the primary data source.
+- All admins and people in the Data Analyst group can create segments on tables they have permissions to query. There aren't additional controls to restrict who can create segments beyond special groups and data permissions.
+- [Only segments on published tables are synced to Git](#only-segments-on-published-tables-are-synced-to-git).
+
+## Further reading
+
+- [Library](./library.md)
+- [Measures](./measures.md)
+- [SQL snippets](../questions/native-editor/snippets.md)
diff --git a/docs/data-studio/transforms/transforms-overview.md b/docs/data-studio/transforms/transforms-overview.md
index 28a4349e14e..74f0f47e100 100644
--- a/docs/data-studio/transforms/transforms-overview.md
+++ b/docs/data-studio/transforms/transforms-overview.md
@@ -240,3 +240,35 @@ Transforms are similar to models with model persistence turned on, but there are
- You can use Python to create transforms.
Use models to enable non-admins to create their own datasets within Metabase, and to add context like field descriptions and semantic types. Use transforms to create persisted datasets in your database and reuse them across Metabase. In future versions of Metabase, model persistence will be deprecated in favor of transforms.
+
+## Convert models to transforms
+
+If you have models you'd like to migrate to transforms, Metabase can convert them for you. When you convert a model, Metabase:
+
+1. Creates a new transform based on the model's query.
+2. Runs the transform to create the output table in your database.
+3. Replaces every question, dashboard, and other item that used the model with the transform's output table.
+4. Converts the original model to a question.
+
+You must be an admin to convert models, and the model's database must [support transforms](#databases-that-support-transforms).
+
+Before converting models into transforms, review [Replacing data sources](../dependencies/replace-data-sources.md) docs for overview and limitations of the process.
+
+To convert a model into a transform:
+
+1. Open **Data Studio** and select **Transforms** in the sidebar.
+2. Click **Tools > Migrate models**.
+3. Find the model you want to convert and click it to open its details panel. The panel shows the model's name, database, and collection, and a list of items that depend on it.
+4. Click **Convert to a transform**.
+5. Fill out the transform settings. See [Create a transform](#create-a-transform) for the overview of settings.
+6. Click **Convert to a transform**.
+
+Metabase runs the conversion in the background. A status indicator at the bottom of the screen shows progress.
+
+If the transform run fails, Metabase stops and leaves the model unchanged—nothing is replaced.
+
+If the transform runs successfully but the source swap fails afterward, the transform and its output table are kept. The model is left unchanged. You can complete the migration manually using [Replace data sources](../dependencies/replace-data-sources.md) to point remaining content from the model to the transform's output table.
+
+Once conversion completes, all content that previously queried the model now queries the transform's output table, and the model becomes a saved question.
+
+Newly created tables will be created with default permissions and will _not_ inherit the model's permissions. As an alternative, consider manually creating and running the transform first, setting up the permissions, then using [Replace data sources](../dependencies/replace-data-sources.md) to swap the model for the transform's output table once you configured permissions.
diff --git a/docs/exploration-and-organization/delete-and-restore.md b/docs/exploration-and-organization/delete-and-restore.md
index c55680c98bc..c21a1b0d996 100644
--- a/docs/exploration-and-organization/delete-and-restore.md
+++ b/docs/exploration-and-organization/delete-and-restore.md
@@ -136,7 +136,7 @@ Segments can be retired. See [Retiring Segments](../data-modeling/segments.md#ed
## Deleting measures
-See [Delete measures](../data-studio/data-structure.md#delete-a-measure). Deleting measures is permanent.
+See [Delete measures](../data-studio/measures.md#delete-measures). Deleting measures is permanent.
## Deleting subscriptions and alerts
diff --git a/docs/exploration-and-organization/history.md b/docs/exploration-and-organization/history.md
index 5a4ee73eb43..487348c0460 100644
--- a/docs/exploration-and-organization/history.md
+++ b/docs/exploration-and-organization/history.md
@@ -44,6 +44,6 @@ Any change to the transform's query or script will be recorded as "changed sourc
## History for segments and measures
-1. Go to the table source for the segment or metrics in [Data studio > Data Structure](../data-studio/data-structure.md).
+1. Go to the table source for the segment or metrics in [Data Studio > Tables](../data-studio/managing-tables.md).
2. Pick the segment or measure in the right sidebar.
3. On the segment or measure's page, go to **Revision history** tab.
diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.md
index 48453d2ec3a..74b9ef0a063 100644
--- a/docs/installation-and-operation/serialization.md
+++ b/docs/installation-and-operation/serialization.md
@@ -307,7 +307,7 @@ Type: Boolean.
Default: Data model is included.
-Excludes [table metadata](../data-studio/data-structure.md) settings, which admins define in **Data Studio > Data structure**. Excluding the data model is useful for subsequent exports where you only want content changes.
+Excludes [table metadata](../data-studio/managing-tables.md) settings, which admins define in **Data Studio > Data structure**. Excluding the data model is useful for subsequent exports where you only want content changes.
### Include field values
diff --git a/docs/questions/metrics-explorer.md b/docs/questions/metrics-explorer.md
index fac185f515d..4495cf9839b 100644
--- a/docs/questions/metrics-explorer.md
+++ b/docs/questions/metrics-explorer.md
@@ -5,7 +5,7 @@ summary: Explore metrics and measures across dimensions and compare them side by
# Metrics explorer
-The metrics Explorer is a space for ad-hoc analysis of [metrics](../data-modeling/metrics.md) and [measures](../data-studio/data-structure.md#measures)
+The metrics Explorer is a space for ad-hoc analysis of [metrics](../data-modeling/metrics.md) and [measures](../data-studio/measures.md)
![Metrics explorer](../questions/images/metrics-explorer.png)
diff --git a/docs/questions/query-builder/summarizing-and-grouping.md b/docs/questions/query-builder/summarizing-and-grouping.md
index b202cd1d902..677d98445f7 100644
--- a/docs/questions/query-builder/summarizing-and-grouping.md
+++ b/docs/questions/query-builder/summarizing-and-grouping.md
@@ -48,7 +48,7 @@ If you summarize and add a grouping you can then summarize _again_. You can also
You can also add metrics and groupings on the results page in a sidebar: the top of the sidebar where you pick the number ("metric") you want to see, and the part below is where you pick how to group that number (or how to "break it out").
-If your admins have created any named [metrics](../../data-modeling/metrics.md) or [measures](../../data-studio/data-structure.md#measures) that are specific to your company or organization, they will be in this dropdown under the **Metrics** or **Measures** section. These might be things like your company’s official way of calculating revenue.
+If your admins have created any named [metrics](../../data-modeling/metrics.md) or [measures](../../data-studio/measures.md) that are specific to your company or organization, they will be in this dropdown under the **Metrics** or **Measures** section. These might be things like your company’s official way of calculating revenue.
By default, Metabase will limit the number of aggregated rows displayed to 10,000 rows. You can change this limit with the environment variable [`MB_AGGREGATED_QUERY_ROW_LIMIT`](../../configuring-metabase/environment-variables.md#mb_aggregated_query_row_limit).