There are a number of "it depends" that might affect the decision.
Generally, the rules of database normalization would be against that, stating that each field should contain only one item of information. The solution in a relational database might be to have a separate table that you join with the primary table. This would allow for multiple rows of data in that relational table to be linked to one row of the primary table.
Now, if that data is only ever going to be retrieved but never searched against, you could probably get away with making it a text column and storing, perhaps, a JSON string that you could use in your application when you retrieve it. But that is going against the usual "rules", so I'm hesitant to just say go ahead and do that without really understanding what that data is modeling and how you want to use it (and might want to use it in the future).