Notes for the record.
Early years. Around Vantage 3.0
Epicor offered fields on a screen that were generic.
You will see them today in tables. Example: OrderHed. UserChar1, UserChar2, UserDate1, UserDate2.
They begin with “User”.
By Vantage 6.0 a Vantage VBFORM tab was added. (Vantage Basic Form)
You could move fields around and resize on this tab.
More Fields were added for you to use. Character01, Character02, etc.
Character, Date, Checkbox and Numeric. One thru 10 each.
Today you can add fields of any name and a “_c” will be added to the end of the field name.
We can also add customized tables.
When do we request a utility to allow us to go back and make things better.
Rename OrderHed.Character01 to OrderHed.InternalSalesDesk_c for example.
I’m not sure this would get a lot of votes if added to IDEAS with all the more pressing issues going on.
I’d say put in an Epicor Idea and rally for votes!
I totally agree - we are looking at this problem right now.
We’ve got to address BAQs, UI layers, RDDs, SSRS reports, etc. where these fields are referenced. It seems like it would be possible to do string substitutions for some of these since these items are kept as objects in the DB tables. They might need regenerating or at least opening/saving in the appropriate editor of course, but it would make things so much easier.
Other objects will need direct attention.
And then there is the copying of data from the old to new column and data type (and other field properties) validation.
It’s doable, but a bit complicated. I’d vote for/comment on an idea for this!
I will be migrating some but not right now. 
Thinking more about this, is this something @klincecum or @Hally would take on? This would be a fantastic utility app - an ‘extra’, not baked in to the platform directly because it’s more of a one-time use program.
I can see a utility to identify the places to modify, but not migrate the code.
Certainly possible for the migration of code and references, but a lot of room for error.
Now for the migration of the data, sure.
Make new field, regen
Copy data, verify, delete old data and or field. Regen again if field deleted.
A utility to identify the places to modify would be immensely helpful. This is on my list of things to do at some point too.
I would create 100 accounts to vote for this
Just to clarify
You are looking for a tool that will identify specific fields and also, check classic customs and bpms for said fields?
Additionally if you could provide a new field name, migrate the data and update any references to the new fields in classic customizations and bpms? This would save a lot of manual leg work if this second option could be created.
Let me know if this covers the scope.
A large portion of it already exists.
https://www.epiusers.help/t/findincode-db-baq-or-why-we-all-love-jgiese-wci/104658
Storing all customizations is a central place to make it easy to search and deploy to various environments?
Exactly