avoid redundancy in multiple controllers in c# code

I'm doing an application that inserts data into 6 different databases. each database has its model and controller and views. the problem is all of them have the same methods with a slight difference here and there but in general, they are all the same. This is redundancy and a lot of similar codes in each controller. Is there a way to reduce that ? would you suggest a design pattern to study to implement it here because I feel what I'm doing here is a bad programming practice, am I correct or just paranoid? Thanks