Data from different tables into one table
What you are proposing is a variant of the so-called "Entity-Attribute-Value" or EAV design pattern.

Aaron Bertrand has an excellent article on the advantages and pitfalls of this design over on SQLBlog.org.

Many people trash-talk EAV, however if done correctly it can be the easiest way to manage diverse sets of data, and is in-fact designed particularly well for your scenario.