Suggestion required for field creation

[Ketan Pandey]

we are migrating to ServiceNow from remedy.in remedy application ,there 253 fields ,all these fields needs to be created on incident.

Please suggest ,Can we create those fields on other table and link taht table to incident table. or any other approch please suggest 

[Adrian Ubeda]

Hello @Ketan Pandey 

If it's mandatory and can not be avoided I think the best approach it's to create a custom table for this (not inherit from Task) and then create fields needed on this new table, and link with incident. With this you will be able to show a related list with fields involved, or show a reference field into incident form. 
However, I'll try to review if this fields are necessary (at least the most of them) and bring business outcomes to the process

[-O-]

I bet one of the reason for migration was that Remedy had 253 field on the incident table.
The question is: do you want to start with SN repeating the mistakes made in Remedy?
I would take the time, normalize the data and place all "extra information" (fields in Remedy that have no correspondent in SN) into variables, or as @Adrian Ubeda suggested, into a new related table.