diff --git a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc
index 1589de28b1..04f5e78c1d 100644
--- a/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc
+++ b/modules/learn/pages/buckets-memory-and-storage/storage-engines.adoc
@@ -116,6 +116,11 @@ In this case, the 1024 vBucket configuration is less likely to have data imbalan
 Also, Magma with 1024 vBuckets uses less CPU for operations such as compaction verse the 128 vBucket configuration.
 * Your applications make heavy use of transactions with persistence-based durability.
 * Your dataset will grow beyond Couchstore's 3{nbsp}TB limit.
+* You can allocate at least 1{nbsp}GiB of memory per node to the bucket.
+The 1024 vBucket configuration gives better performance at scale.
+* You need to replicate into the bucket by XDCR from a cluster running a version earlier than Couchbase Server 8.0.
+Those versions require both buckets to have the same number of vBuckets, and do not support 128 vBuckets, so the target bucket must use 1024.
+See xref:learn:clusters-and-availability/xdcr-overview.adoc[] for the full compatibility rules.
 
 When should you choose Couchstore?::
 You should use the Couchstore backend if any of the following are true: