Yes, it is feasible as long as you answer and solve your specific problem.
As with all software, there is not just a single language or a single technology or a single standard for implementing software. Software should be understood as a solution to a particular problem. The language, technology or standard will depend on a number of variables, such as: Customer needs, customer infrastructure, hardware and licensing costs, labor and knowledge available in your region, software lifetime etc.
For a simple data import program that will be used to migrate from one system to another or from one database to another, if it is used once and then discarded, the design pattern used or the language or libraries it will not matter much because it is not something that will give you maintenance in the future. So, solving your problem today, implement it the way it works and respond well. But if this program is used frequently, and there is a need to maintain, modify or evolve it, think better about this, because other people will have to tinker with the code, so it is good to use a more current pattern, since it is rare to find on the market professionals working with older technologies. Seek consensus with your team or team.