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!

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

Currently when a data deployment template is created, there is no way to edit the template after it is saved so that components can be added or removed. It would be helpful if we could modify the components in the template without having to create the template from scratch again.

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.

Ability to build sequence of data load (choose a list of data load templates and have to possibility to run them automatically in sequence). The sequence can be changed.

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.

Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.

When deploying Data, it would be nice to be able to set field values. It could be just to null them or set a value. It could be part of the configuration or data masking.

Currently, when doing a data deployment Gearset will let you know of all the referenced objects from the object you selected. What it doesn't do is the opposite of that - let you know all the objects that reference your object with a lookup.

It'd be great if we could add a filter to utilize some data pulled in a fetch/query during data deployment.

ex. field (TeamMember.ProjectLookup_c in {returned Project results in query in previous step of data deployment).

New users are often created in the production org that need to be monitored and brought back to sandboxes as well. It would be great if the data deployment tool could support moving user records from prod to sandboxes or scratch orgs.

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

Currently gearset allows to deploy translations from one org to another org, however we do not have an option to do the translations using .stf file /excel for the fisrt time in any one of the org

It should be possible to have gearset to deactivate flows and/or processes based on a selection. And to roll-back afterwards. Similar to what has been created here: https://sfswitch.herokuapp.com/

I would like to see a gearset defined template for Territory Management in Salesforce. I am definitely in need of this functionality as it seems to be a post deployment step once you deployed all Territory Management metadata.

in ETM 2.0 for example, after deploying the related metadata you need to deploy all related records for UserTerritory2Association Object, this contains who are the users assigned to a territory.

Not a big template but can be a good thing to have as a preset.

Having the option to move up only selected fields in a Data deployment is needed. If we are required to move up all fields in each deployment, there are scenarios where our work will get bottlenecked in a sandbox on the way to production and at that point all the deployments will be identical.

Right now there is only an 'And' filter when configuring Fields on the same object. It would make this much more powerful of a tool if we were able to chose between 'And' & 'Or'.

"Select reference fields to deploy"

Ability to edit the value for the target deployment data for the reference field instead of searching for the match on the Target.

Ex. Loading Opportunities from a Source to a Target that contains 5 different record types, but when uploaded to the Target we specify the recordtypeid to one that matches a recordtypeid on the Target for the entire data load.

Similar to how the Owner reference can ignore the Target's users and default to the running user of the data deployment.

It would be useful to select all objects in the data deploy screen to make it faster to select a large number of objects (even better would be the ability to group objects and select whole groups at once)