Hi Hassan,
All of the approaches mentioned her are correct. The part that is going to be tough for you is the OS and DB part. I think what you are going to have to do is first go to 11.2 (on Win2003 / SQL2005), Then upgrade to maybe say 12.5 or 12.6 in that environment. Then replicate the 12.5 or 12.6 environment to a new environment running Win2008/SQL2008. Then upgrade that environment to 14.1. Then you can either stay on that environment, or replicate your 14.1 environment over to another hardware set running Win2012R2/SQL2012. Thats really the only supported way to do this because you are so many releases behind. Something like this is a HUGE project and will take a lot of testing, and a fairly long outage to do when you actually do it in production because you are going to have to go through the migration process multiple times, along with replicating the envionrment at least once, possibly twice - where you have to copy all the attachments, and the database etc. which can take a while.
I would highly recommend engaging CA Services for something like this as they have a lot of experience in migrating much older versions of the product to newer ones.
On another note - what some folks have done in the past is simply start fresh on 14.1 without bringing over any data and starting clean. What they do in those cases is build out a brand new 14.1 system with the latest patches etc. Set it up to work the way they want it to, and then take it live on a certain date. From that date forward, all new tickets are created on the new system. Then they give folks usually 1 to 3 months to close out everything on the old system. If the tickets are not closed out on the old system by a certain date, the analyst (or assignee) must re-create those tickets in the new system and continue to work them from there. Then the old system can have editing rights turned off for all users so that they can only use it to research old tickets but cannot create any new data there. Just food for thought...
Hope this helps you a bit.
Thanks,
Jon I.