diff --git a/code_samples/data_migration/examples/create_product_type.yaml b/code_samples/data_migration/examples/create_product_type.yaml
index 4e9005fa04..950e99cdb5 100644
--- a/code_samples/data_migration/examples/create_product_type.yaml
+++ b/code_samples/data_migration/examples/create_product_type.yaml
@@ -18,6 +18,7 @@
         -   identifier: specification
             type: ibexa_product_specification
             required: true
+            translatable: false
             translations:
                 eng-GB:
                     name: Specification
diff --git a/docs/content_management/data_migration/importing_data.md b/docs/content_management/data_migration/importing_data.md
index ccf17809a7..b6900707ee 100644
--- a/docs/content_management/data_migration/importing_data.md
+++ b/docs/content_management/data_migration/importing_data.md
@@ -213,6 +213,11 @@ The following example shows how to create a content type with two Field definiti
 
 The required metadata keys are: `identifier`, `mainTranslation`, `contentTypeGroups` and `translations`.
 
+The default values of Field definition properties mirror the underlying PHP API, for example:
+
+- `translatable` defaults to `true`
+- `required` defaults to `false`
+
 ``` yaml
 [[= include_file('code_samples/data_migration/examples/create_blog_post_ct.yaml') =]]
 ```