I’m posting this based on a response from Serato Support confirming that Auto Import was intentionally removed as of Serato DJ Pro 4.0 due to “low overall usage statistically.”
While I understand product decisions need to be data-driven, I want to clearly communicate the real-world impact of this change for professional users.

Auto Import was not a convenience feature for me, it was a core workflow tool:

- I manage music externally (finder, scripts, downloads, label drops, edits)
- Files dropped into Auto Import were instantly available in Serato
- No manual drag-and-drop, no rescans, no interruptions during prep

With 4.0+, files still land in:
/Users/username/Music/_Serato_/Imported/Latest Import/
…but never appear in the library, with no UI indication that Auto Import is no longer supported. From a user perspective, this feels like a broken feature, not a removed one.

Why this matters:
- This is a silent breaking change with no in-app warning or migration guidance
- It disproportionately affects power users, working DJs, radio, and production workflows
- It forces unnecessary manual steps or version downgrades
- It introduces risk in live / time-sensitive environments

Request to Product Team:
At minimum, one of the following would help significantly:
1. Restore Auto Import as an optional / advanced preference
2. Provide a new supported workflow that achieves the same result
3. Clearly document and surface the removal in-app (not just release notes)

If usage metrics show low adoption, that may reflect how invisible the feature was, not how unimportant it was to those relying on it daily.

I’m currently evaluating whether I can continue on 4.x or must remain on older versions solely due to this removal. I strongly believe reinstating or replacing Auto Import would improve trust and workflow continuity for professional users.

Thanks for listening, and I hope this feedback is taken into serious consideration.

— Rhype