diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.md
index f253ac386349de3bf42c80076489b6ec8f7b2577..178327ee6470ce48485346f40416f9238f5cce0c 100644
--- a/docs/installation-and-operation/serialization.md
+++ b/docs/installation-and-operation/serialization.md
@@ -14,30 +14,19 @@ To help you out in situations like this, Metabase has a serialization feature wh
 
 If you're looking to do a one-time migration from H2 to MySQL/Postgres, then use the [migration guide instead](./migrating-from-h2.md).
 
-### What gets dumped and loaded
+## What gets dumped and loaded
 
-**Currently, dumps consist of the following Metabase artifacts:**
+Only some artifacts are included in dumps and loads:
 
-- Collections
+- Collections (except for personal collections)
 - Dashboards
 - Saved questions
 - Segments and Metrics defined in the Data Model
 - Public sharing settings for questions and dashboards
-
-**They also contain a number of system settings:**
-
 - Admin Panel settings, except for permissions
 - Database connection settings
 - Data Model settings
 
-**Dumps do _not_ contain:**
-
-- Permission settings
-- User accounts or settings
-- Alerts on saved questions
-- Personal Collections or their contents (except for the user specified with the `--user` flag; see below)
-- Archived items
-
 ### Before creating or loading a dump
 
 If your instance is currently running, you will need to stop it first before creating or loading a dump, unless your Metabase application database supports concurrent reads. The default application database type, H2, does not.