You've watched the progress bar freeze at the same percentage more than once. It's not random, and it's not your internet connection.
BigCommerce's own guidance is blunt about this: don't try to import more than a few hundred items at once. Push past that with a single large file, especially one with a lot of images attached, and the import is more likely to stall somewhere in the middle and just sit there.
The usual fix BigCommerce recommends is splitting the file into smaller batches and re-importing piece by piece until you find the row that's actually causing the problem. That works. It's also exactly the kind of thing nobody wants to spend an afternoon doing, especially when you've got a few thousand SKUs that all need to move at once, not a few hundred.
The real issue isn't your file. It's that bulk imports were built for occasional, moderate-sized updates, not for running a catalog that changes by the hour because a distributor feed is constantly shifting underneath it. If you're stitching together CSV exports and re-imports as your actual ongoing process, you're fighting a tool against the exact thing it wasn't built to do repeatedly.
We don't run your catalog through a CSV import at all, and that's the actual fix, not a workaround for it. New items from your distributor get pulled in, processed, and pushed live continuously through a direct connection to your store, the same way we've already done it for catalogs with over 130,000 live products. There's no batch to split, no progress bar to babysit, no bad row to go hunting for after the fact.
If you just migrated your store to BigCommerce, this is one of several things that tends to surface in the first few weeks.
Done babysitting import progress bars? So are we.
Talk to Us →