Instance Backup & Restore allows you to export requests and admin configurations from one instance to another. Always restore data to a new instance to maintain data integrity.
Role Required: SDAdmin
The following entities are exported during instance backup & restore:
|
Category |
Entities |
Exceptions |
|
General Configurations |
Domain, Organization, Region, Site, Department, Support Group (with role associations), Group Roles, User Group, Holidays, Operational Hours, Leave Types, Users, Technicians, Roles |
- |
|
Admin Configurations |
Status, Category, Subcategory, Item, Level, Mode, Impact, Urgency, Priority, Request Type, Task Type, Work Log Type, Announcement Type, Request Closure Code, Additional Fields (Request/Task/Work Log), Templates (Incident/Task/Reply/Work Log/Resolution), Service Category, Service Catalog |
Additional fields with reference entities, approval configurations, and Field and Form Rules are not included |
|
Request-Related Configurations |
Requests, Notes, Conversations, Resolutions, Work Logs, Tags, Tasks, Task Work Logs, Task Comments and Replies, Task Tags, Attachments, Inline Images |
Archived requests are not included |
To backup an instance,

Restore the instance from the .ezip backup file.
To restore an instance,

After restoration, only the summary page will be displayed under the Restore tab, showing:

Click entries in the Failure column to view failure logs.

During restore, Support Groups and Roles are renamed in the target instance to avoid conflicts.
|
Entity |
Behavior |
Format |
Example |
|
Roles |
The role name is modified. |
<RoleName>_<HelpdeskName> |
Technician to Technician_TravelHelpdesk |
|
Support Groups |
The support group email ID is modified |
<HelpdeskName>_<GroupEmailID> |
support@traveldesk.com to TravelHelpdesk_support@traveldesk.com |
You can back up and restore requests based on sites by modifying the instanceBackupRestore.json file.
Add the following search criteria under the extraListInfoForFetchingEntity key for the request entity, and replace <sitename> with the required site name.
This ensures that only requests associated with the specified site are included in the backup and restore process.