Migrating Large Attachments to a ServiceNow Instance

When migrating to a ServiceNow instance, the attachment size is limited to the value defined in the Advanced Execution Options.  Any attachments larger than this are excluded from the migration but included in the migration report.

It is recommended that the maximum size of any attachment does not exceed 32MB and that the attachment size limit be set to a value less than or equal to this.  

When migrating large attachments to a ServiceNow instance, if the migration takes more than 60 seconds then a time-out will occur. The following message may appear in the log and the migration report for the corresponding table mapping:  Failed to Post Attachment Data: Failure during REST Call. 

If this occurs, you can increase the timeout on the target ServiceNow instance by selecting System Definition -> Transaction Quota Rules from the menu (requires administrator permissions).  Update this record by increasing the default limit (60 seconds) to a suitable limit based on the size of your attachments and the speed of your network connection.

In some situations when migrating large attachments, the migration may indicate a failure to connect to the target server after 60 seconds.  If the target server is still accessible using a web browser on the same desktop client then it may be necessary to increase request_processing_timeout.  To do this, navigate to the sys_properties table (requires administrator permissions), and search for the entry called:  glide.soap.request_processing_timeout.

Update this record by increasing the default timeout (60 seconds) to a suitable limit based on the size of your attachments and the speed of your network connection.  The re-run the migration.