Currently Data Deployments only allow filtering on
[FIELD] = [VALUE]

It would be beneficial to be able to include other logic operators such as:
NOT EQUALS
LIKE
IN
GREATER THAN
LESS THAN

etc.

Allow complex filters and child relationships on filters for data loading. For example, filter the Account to only load if the Owner is an Active user in the system.

When I do a deployment it would be useful to download the success and error logs as a csv or excel document

Please add the ability to use the "Compare and Deploy" for Attachments and Files. The ability to migrate PDFs, image files, word docs, and excel spreadsheets would be GREATLY appreciated! Thanks!

The current data deployment functionality works fine for one-off deployments, but if you are trying to keep specific data in sync across multiple orgs, the ability to schedule data deployments for a given time in the future would let you deploy on a recurring basis automatically. Becomes especially helpful when combined with the current data filtering options.

When deploying data records, it would be helpful if audit fields values could be migrated

During a data deployment it should be possible to mask the data in specific fields. For example, if I were importing Account and Contact data from production into a sandbox I would want to be able to mask email address so that we can't erroneously send actual customers emails while we're testing

When copying data from production to sandboxes we need to be able to anonymise it for data protection, i.e. GDPR. We also do not want to accidentally email anyone from non-production systems.

Provide options to delete records from Target Org. This will help clean up of test data and reload from Source.

When we pull down a version between our local and staging environments. We would like to also automatically pull in the testing data from another project.

As one of the things we are trying to setup is taking a version from Prod then running GhostInspector through our core flows. Ideally every 4 hours we take a backup from metadata + locked down actual data. Then run tests against it.

Show source Org records count for each object so that we can decide on how much of it can be moved and how much of filter is needed. Moreover after all object are select with filters for movement, please show the total number of records that will be migrated across all selection and its related objects. This will tell us if we are exceeding the limit of 10000 and do we need to split.

It would be very helpful to some processes I run if I could do data deployment filtered based on date - date created specifically. I am trying to migrate some test data from Production to QA/User Testing and I get duplicates now. A filter on created date would solve the problem entirely.