Attachments and Options

Attachments

In most migrations, file attachments are migrated as part of the form mapping (if required) rather than in a separate form mapping. For example, if you are migrating incident records, you can choose to migrate the attachments for these incidents as well.

This can be set on the Options tab, though note that attachment migration is not supported for all migrations. To see if your migration will support attachment migration, check the Attachment Support Matrix.

For some source adaptors (notably BMC Remedy), attachments are stored in fields on the table itself. For these source server servers, you can select the fields you want to migrate.

For a BMC Remedy target, attachments are stored in fields on the table itself. For these target server servers, you must select the select the attachment field fields you want to populate.

It is recommended to enable attachment migration ONLY if you are sure that attachments exist on the source records. Even if no attachments get migrated, Precision Bridge will need to perform operations to check for source attachments and this will decrease performance.

Other Form Mapping Options.

There are many other options that can be specified for form mappings, but we won't go through them all.

Two options define what to do if the record already exists (i.e. should the migration update records) or what to do if the record does not exist (i.e. should the migration create new records)

Some target servers support different methods of performing the target insert/update (migration methods). Usually, the default option selected will be the best one. Be sure you understand how each works if you elect to change these.

For Service Now target migrations, you can also specify whether to run business rules. If the source is also service now, you can specify whether to keep the same sys_id (it is recommended to do this unless there is a good reason not to as it will generally simplify the migration field mappings)

The options on the 'Advanced' tab generally relate to performance tweaking and additional validation and can in most cases be left to their default values.

For a fuller description of all the Form Mapping options available see: Form Mapping Options