Ability to change field type for collection fields

I often have that as a website and its content grows I need to change what used to be a plain text field into a rich text field. Or a numbers field into a plain text one.

Now the only way to do this is very labor-intensive... create the new rich text field, copy-paste all the old content from the plain text field into the new rich text field and then go into the pages that have that collection in it and connect it to the new rich text field.

A simple option in the Collection to alter the field type would be such a time saver.

  • Marcel Deelen
  • Jan 13 2020
  • Reviewed
  • Jacob Schlegel commented
    30 Sep, 2023 12:13pm

    YES! Little things like this would be so helpful.

  • Joachim Wernersson commented
    7 Sep, 2023 09:14am

    Yeah this would be a great feature

  • Jon Q commented
    22 Jul, 2023 06:21pm

    I just ran into a need for this. Being able to convert a plain-text field type to rich field would be very helpful :)

  • Brian Dawson commented
    18 May, 2022 01:24pm

    I really didn't want to copy/paste data from my old field to a new field, so I used Parabola as a workaround.

    Essentially, here are the steps:

    1. Create new field in collection.

    2. Create Parabola flow

    3. In Parabola flow:

      1. Pull in collection and all its fields

      2. Add a "Send to Webflow" step

      3. Set up that step to overwrite the new field (which would be blank) with the old field's data.

    Possible in about 5-15 minutes if you're familiar with Parabola.

    I wrote up my use case as an example, here.

    Hope that helps someone.

    But still, allowing field changes within a collection would make things much simpler!

  • Jennifer BeVard commented
    30 Mar, 2022 10:16pm

    I've come up against this with Text Fields. Requirements change and it would be nice to convert it to a Rich Text Field.

  • Vinícius Sgarbe commented
    9 Mar, 2022 07:48pm


  • Bryan Perdue commented
    26 Jul, 2021 07:57pm

    Please do this

  • SGFCreatives commented
    17 Jul, 2021 09:49pm

    Literally dying for this.

  • Bruno commented
    28 Jun, 2021 12:41am

    Yes, this feature is much needed. Please bump.

  • Shafic Rawdah commented
    24 May, 2021 07:28pm


  • Michael Payne commented
    17 May, 2021 10:57am

    Yes, this would be a really useful addition

  • Joel Downs commented
    16 Apr, 2021 09:45pm


  • Zack Steven commented
    10 Mar, 2021 06:01pm

    This is much needed. In my case, members are linking to their personal websites but inevitably don't insert a valid URL. When Memberstack goes to update their corresponding CMS item, Zapier returns an invalid URL error message. We should either be able to change the type of a CMS field or URL validation in forms should be an option alongside email, phone, etc.

  • Thinklittle commented
    18 Feb, 2021 12:08am


  • Colin Chaloner commented
    24 Jan, 2021 03:09pm

    Argh. Yes, this is definitely needed. Torn between re-importing & relinking everything to fix, or replacing all plain text elements with rich text. Neither ideal. Ability to change after the fact would make a huge difference.

  • Alexandra Sloves commented
    26 Nov, 2020 01:33pm

    NEED :)

  • Sonia Morales commented
    13 Aug, 2020 06:14pm

    Need This!!!

  • Matthew Craig commented
    4 May, 2020 09:12pm

    Up vote...

  • Padam Raj Shahi commented
    22 Mar, 2020 09:49pm

    Yeah Exactly I am also voting for this

  • +54