Over time your organisation may need to change the MoveData authorised user. To do so:

When changing the MoveData authorised user, there are two additional things you should be aware of:

The new authorised user should have at least the same permissions as the outgoing authorised user.

For example, if the outgoing authorised user has read and write permissions for a field being set by the integration, and the new authorised user does not have read and write permissions for that field, then the integration would error once switched over to the new authorised user (since it no longer has read and write permissions to that field).

In most scenarios, if you ensure the new authorised user has the same profile as the outgoing authorised user you should be OK.

Specific duplicate rule conditions may be exist for the outgoing authorised user. When changing the MoveData authorised user, we recommend you review your duplicate rule conditions and, if needed, update them to reflect the new authorised user.

In practice this typically invoices updating any include / exclude logic away from the outgoing authorised user and to the new authorised user instead. For example, if you have a filter condition for the outgoing user alias of movedata, and the new authorised user has an alias of newuser, you would edit the duplicate rule condition and change from movedata to newuser.

You can find more information on how MoveData works with your Salesforce Duplicate and Matching Rules here.