Workflow for importing Excel to List

Your overall plan is pretty sound, and Rob's point about pagination is the one I'd watch most closely if you go the Power Automate route — that 256-row default catches a lot of people out on a first import.

One thing worth trying first, though: if this is a one-off load rather than something that will keep repeating, you may not need the flow at all. Lists can create a list straight from an Excel file, columns and all, and then you can tidy the column names and types in List settings afterwards. That saves building a flow just to move rows once, and it also gives you a quick way to see how SharePoint reads your headers and date columns before you commit to anything.

If the file will keep coming in, or you need the cleaning steps to run the same way every time, then your flow makes sense. Just make sure the Excel data is in a proper table with a single header row, no blank rows at the top and the same kind of value all the way down each column — mixed text and numbers in one column is usually what trips an import up.

On the time zone bit, I'd sort the site's regional settings out before you judge any of the imported dates, because a wrong setting there can make perfectly good dates look shifted. Once that's right, run a small batch first, check a few date and choice columns by eye, and then do the full run. Your step 4, repeating until it's clean, is exactly the right instinct — it's much easier to fix the source file and re-run than to clean up rows after they've landed in the list.