I kind of vaguely remember OOP from school.
I think though, when I say a bunch of imports, I am somewhat giving off the wrong impression. Though they are imports, there are so many specific things going on besides the actual import that for the fact that there ARE a limited amount (I think it's actually closer to 25-30 than the 60 I originally thought) it is probably still an easier approach to just handle each one by one than set up objects.
For instance, on the phone marketing import I have to first find all the customers that will be excluded from being imported into the table. So you have to grab from one table to see if a customer has a "do not call" etc. request connected to them. Then you need to exclude all customers in the bankruptcies database, because we're not allowed to contact customers in bankruptcy proceedings. Then you exclude those connected to dealers we no longer support... that's another table. Then there are a few more exclusions from a completely different database... well, 4 different databases. I can't really get those into our current database without redoing a lot of design done before I got here and well, this project is supposedly supposed to be done by Christmas, so that's not happening.
So now we can finally import from the customer + account + a few other tables with fields we need... into the phone marketing table for each of our two companies.
And then we use those to create what are called "non" phone marketing tables (I have no idea why, the name is very deceiving) which are, essentially, taking any customer who is a customer of one of the companies but NOT of the other and giving that data to the other so they can market to that customer.
This whole design is a bit different than say... importing into the delinquent account tables. Which you would think would be as simple as calculating who is delinquent and who isn't, but yet again there is a lot more specific stuff involved in determining what "delinquent" even means.
So while a lot of this could all be set up with classes and objects, most of it is very specific stuff that simply isn't done on the other imports. The only obvious similarity is that, eventually, fields get imported into a database. But that part is just a few lines of code, the "massaging" is the bigger part. Is it really worth it to go OOP when the imports, as it stands, are all already working on their own pages?