# Yaml format supported for import

**URL:** <https://forums.pega.com/t/yaml-format-supported-for-import/11275>\
**Category:** Blueprint and App Design\
**Tags:** pega-platform\
**Created:** [March 23, 2026, 10:51am UTC](https://forums.pega.com/t/yaml-format-supported-for-import/11275 "2026-03-23T10:51:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ChrisBoone](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/chrisboone/32/22821_2.png) [@ChrisBoone](https://forums.pega.com/u/ChrisBoone)\
**Post date:** [March 25, 2026, 4:46pm UTC](https://forums.pega.com/t/yaml-format-supported-for-import/11275/3 "2026-03-25T16:46:29Z")

</div>

I have been able to use YAML to import data structures. When I did it, it was not because I was trying to connect to a service, but because I had 250 properties defined on my case (from ideation) and I wanted to quickly reorganize those properties into classes. When I did it, I used a spreadsheet to work through what my target data model should be and then used copilot to generate a YAML to import the target data model into my blueprint so I could import it. (Co-pilot was not perfect.)

Here is an image (can’t attach a file) of what your YAML should look like to be accepted:

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/6/4/64d47302cc6f04e247d6e50cc38bb18ec2d6a5f0.png)

You don’t have to include a description, but if you do, the properties will have that description.

if you get a data type wrong, for example using Text instead of string, the property may not import. I have also had cases with large YAMLs where I had to search for errors (thanks co-pilot) to get them to import.

If you see an object identified after doing your upload, you are half way there.

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/8/8/88b1ed27ca643d407b44cdd009038aff39eb738e.png)

Your schema will be tested more thoroughly when hitting submit and other errors can prevent the import. This can be very aggravating.

Post upload, I recommend updating your labels for your fields as the labels and IDs will match what you imported. Doing this, you should be able to cleanly import your defined classes.

I also recommend doing a test import into another blueprint to verify what you are getting as you can’t delete embedded data classes should you decide you want to reimport after making corrections.

---

_[View the full topic](https://forums.pega.com/t/yaml-format-supported-for-import/11275)._