diff --git a/src/content/changelog/r2/2025-12-04-r2-super-slurper-select-object-migration.mdx b/src/content/changelog/r2/2025-12-04-r2-super-slurper-select-object-migration.mdx
new file mode 100644
index 000000000000000..c73a86d9acd84d5
--- /dev/null
+++ b/src/content/changelog/r2/2025-12-04-r2-super-slurper-select-object-migration.mdx
@@ -0,0 +1,32 @@
+---
+title: Super Slurper now supports selective object migration
+description: Super Slurper now supports migrating specific objects by key.
+products:
+  - r2
+date: 2025-12-04
+---
+
+[Super Slurper](/r2/data-migration/super-slurper/) now supports selective object migration, allowing you to specify up to 10,000 specific objects per migration job to copy from your source bucket to [Cloudflare R2](/r2/).
+
+With selective migration, you can migrate specific objects according to your needs without copying an entire bucket or prefix, or easily retry objects that failed to migrate from a previous Super Slurper job.
+
+In the Dashboard, when setting the Source bucket options, use the **Specific object keys** option to list up to 10,000 objects using newlines as the delimiter, or upload a CSV file containing your list of object keys.
+
+To use selective migration via the API, include the `keys` array in your request:
+
+```bash
+curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/slurper/jobs" \
+--header "X-Auth-Email: $CLOUDFLARE_EMAIL" \
+--header "X-Auth-Key: $CLOUDFLARE_API_KEY" \
+--header "Content-Type: application/json" \
+--data '{
+  "source": {...},
+  "destination": {...},
+  "keys": [
+    "path/to/object1-key.pdf",
+    "object2-key.csv"
+  ]
+}'
+```
+
+For more information, refer to [Super Slurper documentation](/r2/data-migration/super-slurper/).
diff --git a/src/content/docs/r2/data-migration/super-slurper.mdx b/src/content/docs/r2/data-migration/super-slurper.mdx
index aa3d4fb9a32dff6..fba4d6036c1e336 100644
--- a/src/content/docs/r2/data-migration/super-slurper.mdx
+++ b/src/content/docs/r2/data-migration/super-slurper.mdx
@@ -39,10 +39,18 @@ You can view the status of your migration job at any time by selecting your migr
 
 ### Source bucket options
 
+Each migration job can filter objects by either a sub path prefix or a list of specific object keys, but not both.
+
 #### Bucket sub path (optional)
 
 This setting specifies the prefix within the source bucket where objects will be copied from.
 
+#### Specific object keys
+
+This setting allows you to specify up to 10,000 specific objects per migration to copy from the source bucket. Use this option when you need to migrate a defined set of objects rather than an entire bucket or prefix.
+
+Objects specified in your list that do not exist in the source bucket will return an error status in the migration results.
+
 ### Destination R2 bucket options
 
 #### Overwrite files?