Creating Child table using already existing data

[tahnalos]

My current client has been making modifications to the Location Table for several years now, adding various fields to the table.  They use several types of location entries, each requiring different fields for each type.  This was pointed out to them as a potential maintenance issue but was ignored.

During an upgrade to Jakarta, there were several issues with the data on the location table.  ServiceNow engineers have identifed the problems as due to updates to the Locations table itself and impacting the data on these fields.  They have recommended that child tables be extended from the Location Tables and the fields added moved to each child "type".

Is there a quick and effective way to "move" certain fields to the child table?  Is there a quick and effective way to "move" data to the child table?  Barring that, if we need to create the new fields and retire the old ones on the original table, is there any way to determine which fields are being used or not?  The client added about 200 new fields on the location form, and most of them on first glance appear to be empty with no data.

Please help.

Thanks

[Stewe Lundin]

To be honest I don't know, how to solve the integration, I don't know how it's set up and whats what. 
If it gets to messy Id rewrite it from scratch and plan this trough before I'd go to action.

But yes I guess it's going to get messy. 

Good luck. 

Let me know how it pans out.