Migrating Attachments from a Salesforce / Remedyforce Instance

Salesforce has two different ways of storing attachments. In the Classic version, attachments are commonly stored in the Attachments table. However, in Salesforce Lightening Experience, attachments are more commonly stored as files. Precision Bridge supports both, but you will need to identify for each form mapping which method is used. Note that it is possible that a single record has attachments stored in both ways - This may be the case if some users are using Salesforce Classic, since the ability to add 'Attachments' directly (as opposed to via a work note or comment) is often visible in the UI in the Classic view.

When selecting the attachment support option (on the Options tab of the Form Mapping), you will see that there are three possible options.

Select the one that is appropriate to the Salesforce/Remedyforce table you are migrating from. This will usually depend on whether your users are using Salesforce Classic or Lightening experience and how they can add attachments/files. If you are in any doubt, it is best to select 'All Attachments and Files' If this option is selected, Precision Bridge will check both locations.

Handling Duplicate Attachment Names

To prevent any issues with duplicate attachment names (which some target systems cannot support) you can optionally prepend the id of the attachment to the filename to ensure uniqueness. This option can be found on the Options->Advanced tab of the form mapping.