# Change Custom Type — 2022

**URL:** <https://community.prismic.io/t/change-custom-type-2022/11192>\
**Category:** Developing with Prismic\
**Created:** [September 26, 2022, 1:09pm UTC](https://community.prismic.io/t/change-custom-type-2022/11192 "2022-09-26T13:09:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank.stallone](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/frank.stallone/32/4834_2.png) [@frank.stallone](https://community.prismic.io/u/frank.stallone)\
**Post date:** [September 26, 2022, 1:09pm UTC](https://community.prismic.io/t/change-custom-type-2022/11192/1 "2022-09-26T13:09:16Z")

</div>

[I see a previous topic from years ago asking about to change Custom Types](https://community.prismic.io/t/how-to-rename-a-contenttype-in-prismic/2731). The answer has links to articles that no longer resolve. Things have changed since years ago. On Prismic's modern stack I don't expect much has changed in the way of 'renaming' a Custom Type but let me explain what we have and what we want to do:

- Created a Custom Type `documentation_page`
- Created two pages with this `documentation_page`
- Used it for `linkResolver()` to create pages based on `documentation_page`
- Realized we wanted to call this `components` instead of `documentation_page`

Is there a way we can re-associate all of the `documentation_pages` with a new Custom Type called `components`? I know we can rename the Custom Type, but in code we're still looking for `documentation_page` which will cause confusion. I want to keep naming consistent. How can we make this happen?

---

<div class="post-metadata">

**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\
**Post date:** [September 26, 2022, 8:59pm UTC](https://community.prismic.io/t/change-custom-type-2022/11192/2 "2022-09-26T20:59:20Z")

</div>

Hey @frank.stallone, thanks for reaching out.

It isn't possible to associate an existing Custom Type to the documents of a new one. You will need to copy the content of the existing documents using the new Custom Type components and then gradually replace references to it in your code.

The documentation and articles have indeed changed over the years. I have updated the links in the thread to be more accurate.