It's 5:30 on Saturday morning and I'm waiting to catch an Uber to the airport. While packing up my suitcase I couldn't help but reflect on the past three days spent at Laracon, an annual gathering of Laravel developers in Louisville, Kentucky.

As a Junior Engineer at Zaengle, I’ve learned that writing good clean code is one of the most important aspects of being a developer. There are many places in code where logic can get out of hand quickly. One such place is in the controllers. We sometimes think that the controller is simply a place to dump any logic we don’t quite know what to do with.

Importing data into a Laravel app from CSV may be accomplished in many ways... here's how I do it!

In the previous article we created the CSVUpload, gathered the column mapping, and split the data into individual CSVRow records. At this point we are ready to implement the business-specific rules for integrating the data into our application.

If you've made it this far, you already know that we've imported data from a CSV file, mapped the columns into our application's domain, split the data into individual rows, and set up a Laravel Pipeline to ingest the information.