How to organize a data import module in my SAAS that respects dependencies between records?

Hello friends, I hope you are well! I tell you that now in my SAAS I am working on the data loading part of my clients, this stage is or should be the initial one so that when I start using the SAAS, I have all the data entered in the different modules, I had worked a certain part where I added some import and export buttons but I think that for usability and precision it is much better to have a module or section exclusively for importing data... So my question is if I can place a cluster within another cluster, since I think it would be interesting to be able to place another cluster in configuration that allows importing each registration of the system modules that are required, for example having a subcluster to import EntrustRegistration with the button for import and export the demo for excel, other cluster to import VisitRegistration, other cluster to import PropfIncome and so on, is this an idea that occurs to me at the moment... or do you suggest a simpler idea to cover this section? The idea of ​​having several subclusters is to be able to enable the next import only if records were imported in the previous cluster, since there are imported data that depend on others! For example, payments depend on suppliers, so these payments are related to a supplier, therefore I cannot import payments first and then suppliers...