# Fix Internal Values for Custom Lifecycle Stages **URL:** \ **Category:** HubSpot Ideas\ **Tags:** properties\ **Created:** [November 29, 2022, 8:15pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198 "2022-11-29T20:15:45Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![KSchlarf](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kschlarf/32/41516_2.png) [@KSchlarf](https://community.hubspot.com/u/KSchlarf)\ **Post date:** [November 29, 2022, 8:15pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/1 "2022-11-29T20:15:45Z")
I love that we can customize Lifecycle Stages in the new Contact area, however there is a quirk in this roll out. Why are custom Lifecycle Stages given a number string and the standard options are using text? You should either make new ones generate a text string internal value to match the given name and the existing option formating OR let us edit the internal values on Custom Lifecycle Stages. This makes it messier for using this field with APIs. ---
**Author:** ![trangnguyen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/trangnguyen/32/14279_2.png) [@trangnguyen](https://community.hubspot.com/u/trangnguyen)\ **Post date:** [May 19, 2023, 5:58pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/2 "2023-05-19T17:58:49Z")
I agree with OP. It would be great to be able to customize the internal value of the custom lifecycle stage as a text string when we use it for API calls. Prior to the roll out of customized lifecycle stages we were able to update and change the internal value by remove the underscores. ---
**Author:** ![MMaurer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mmaurer/32/44643_2.png) [@MMaurer](https://community.hubspot.com/u/MMaurer)\ **Post date:** [June 30, 2023, 10:05pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/3 "2023-06-30T22:05:39Z")
Agreed! I’m working with a client who’s creating a fully customized lifecycle to fit their business needs and I would love to be able to edit these internal values. It’s not helpful to see these coming through with a string of numbers / not have the option to set the internal value when creating the new lifecycle stage. ---
**Author:** ![JOB3](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/job3/32/16381_2.png) [@JOB3](https://community.hubspot.com/u/JOB3)\ **Post date:** [February 1, 2024, 4:42pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/4 "2024-02-01T16:42:02Z")
+1 ! I have worked with several customers that said they would benefit from this change in the custom lifecylcle stages. It would make it specially easier to indentify lifecycle stages when connecting HubSpot with other applications and also would make the reports more easy to comprehend. ---
**Author:** ![Pinarav](https://avatars.discourse-cdn.com/v4/letter/p/a5b964/32.png) [@Pinarav](https://community.hubspot.com/u/Pinarav)\ **Post date:** [June 24, 2024, 7:53am UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/5 "2024-06-24T07:53:03Z")
Fully agree! We have one custom lifecycle stage value and the overall picture looks a little messy now. Any update here to edit the internal values of custom lifecycle stages? ---
**Author:** ![2kan](https://avatars.discourse-cdn.com/v4/letter/2/c68b51/32.png) [@2kan](https://community.hubspot.com/u/2kan)\ **Post date:** [August 5, 2024, 12:46pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/6 "2024-08-05T12:46:02Z")
100% it does not make any sense that the default lifecycle stage internal values are not numeric, and then when you create one yourself it becomes a numeric ID. The fact that with all other properties the default internal value name is the label name in all small letters and no spaces, only adds to the fact that this would be the most logical way forward for deal stages as well. This would already help, but of course having the option on creation to edit the internal value is at the end what you really want, and should be there. ---
**Author:** ![CarlosM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/carlosm/32/81360_2.png) [@CarlosM](https://community.hubspot.com/u/CarlosM)\ **Post date:** [September 19, 2024, 7:35am UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/7 "2024-09-19T07:35:42Z")
This is definitely needed. We have a third-party integration that is reading the internal value and it’s causing a massive headache! ---
**Author:** ![AStenbeck](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@AStenbeck](https://community.hubspot.com/u/AStenbeck)\ **Post date:** [October 7, 2024, 12:16pm UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/8 "2024-10-07T12:16:01Z")
We really need this for invoice API!!! ---
**Author:** ![mackmotion](https://avatars.discourse-cdn.com/v4/letter/m/94ad74/32.png) [@mackmotion](https://community.hubspot.com/u/mackmotion)\ **Post date:** [July 2, 2026, 12:12am UTC](https://community.hubspot.com/t/fix-internal-values-for-custom-lifecycle-stages/70198/9 "2026-07-02T00:12:02Z")
Agreed - it’s 2026 and we still need this updated. As someone who does a lot of external automations, having StageIDs be customizable would make my working with HubSpot way more efficient. Having to make a list of the Stage IDs as numbers and which Stages they relate to feels redundant.