Instead of processing everything, you can define exactly what should be included in a job. For example, many Shoviv products allow filtering based on:
- Date range (migrate only recent or older items)
- Folder selection
- Item type (emails, contacts, calendars, etc., depending on the product)
- Subject or sender criteria
- Include or exclude specific folders
- User or mailbox selection
- File extensions (for cloud storage migration tools)
Another advantage is reducing migration time. By excluding unnecessary items, the migration engine processes less data, which can improve overall performance and reduce storage consumption at the destination.
For organizations handling multiple migration projects, customized filters also make it easier to create different jobs for different departments or users without manually sorting data beforehand.
Of course, it's always a good idea to review the filter settings before starting a large migration. Running a small test job first helps confirm that the selected criteria return the expected results.
Overall, customizable filters may seem like a small feature, but they can make migration and backup tasks much more efficient while giving administrators better control over what data is processed.
I'm curious how others use filtering in their migration projects. Do you rely mostly on date-based filters, folder selection, or something more specific?