It looks like we don't have the translated page you're looking for, but we do have other content in English and offer support in English.
Account admins on paid accounts can perform account backups. On Enterprise accounts, it’s possible to restrict admins from performing account backups.
⏱ 4 min read
You can perform an account backup to save a local copy of your account's Wrike data.
Account admins can run account backups and backup data related to Tasks, Folders, and Projects which are shared with them. When performing an account backup, account admins are not able to backup data related to Tasks, Folders, and Projects which are not shared with them.
Backed up | Not backed up |
Tasks, Folders, and Projects with their descriptions and time logs | Data in the Recycle Bin |
File attachments stored in Wrike | Files attached from integrated storage facilities (Box, DropBox, Google Drive) |
Comments | History of task updates from the Activity Stream |
User info: names, e-mails and IDs |
Account Backups without attachments can be requested once a week.
Please note, account backup links are only valid for 7 days.
You can run a backup, which includes attachments, using Wrike’s Backup Tool. To download the backup tool:
Please note: You must be familiar with the command line script to run this application.
You must have Java Runtime Environment (JRE ver.8) installed. Run the "java -version" command in the command prompt to check your Java version and update it if necessary.
* If you don’t see this option on Windows 10, you can skip Steps 2 and 3 and proceed to manually opening the “backuptool-win.exe” file.
Required (Before you Start):
Please make sure you have Java Runtime Environment (JRE ver.8) installed. Run "java -version" in your terminal to check your version of Java and update it if necessary (http://java.com/getjava).
The backup tool creates a folder /backups/account-<accountUID>/. Inside it there are two folders - /attachments/ and /backup-<backupUID>/. The folder /attachments/ holds all the latest versions of attachments stored in Wrike, individual files follow the naming convention <attachmentUID>-<attachment_file_name>. The folder /backup-<backupUID> contains a zip archive backup-<backupUID>.zip.
The archive has four files in it:
users.json
users.json - JSON array of users (firstName, lastName, uid, email, userType: {1 - regular user, 2 - invited user})
[
{
"firstName":"name1",
"lastName":"name2",
"uid":"U2CBMkbSnC9T",
"email":"email@email.tom",
"userType":1
}
]
folders.json
[
{
"id": 16902506,
"children": [21821807, 21821804, 21821749, 21821745, 17006046],IDs of non-deleted folders that reside inside the current folder
"title": "title",
"author": "U2CBMkbSnC9T",UID of the user who created the folder
"dateCreated": "2013-09-02 12:29:24",
"description": "description",
"shared": ["U2CBMkbSnC9T"],An array of user UIDs that have access to the folder
"comments": [
{
"body": "U2CBMkbSnC9T",
"author": "U2CBMkbSnC9T",
"dateCreated": "2013-09-02 12:29:24"
},
{
"body": ".333",
"author": "U2CBMkbSnC9T",
"dateCreated": "2013-09-02 12:29:24"
}
],
"attachments": [this array does not contain attachments from Google Drive, the follow as a separate array
{
"contentType": "application/octet-stream",
"version": 1,
"parentId": 2067818, ID of the folder that the file is attached to
"description": "",
"apiId": "IEAAAEDYIYAB7DLK", Attachment UID that is used to match the file in the /attachments/ folder of the backup with the data in the JSON file
"attachType": "External",
"id": 2067818,
"name": "test+doc+box.webdoc",
"dateUploaded": "2013-04-29 04:48:34"
}
],
"googleDocs": [
{
"resourceId":"1NPu0BlX9hrnSZf1OYh9TyFDoJWEYWxXiC2c01m6PnuY",Google ID of the file
"id":2000736,
"name":"test document.doc",
"dateUploaded":"2014-09-02 19:56:43"
}
]
}
]
Possible values of the attachType:
Legacy
Temp
External
ASPost
Task
tasks.json
The structure is similar to folders.json with a notable exception that tasks do not have children (tasks and subtasks are listed together and have no distinction).
[
{
"id": 16902506,
"title": "title",
"author": "U2CBMkbSnC9T",UID of the user who created the task
"dateCreated": "2013-09-02 12:29:24",
"description": "description",
"shared": ["U2CBMkbSnC9T"],array of user UIDs who have access to the task
"comments": [
{
"body": "U2CBMkbSnC9T",
"author": "U2CBMkbSnC9T",
"dateCreated": "2013-09-02 12:29:24"
},
{
"body": ".333",
"author": "U2CBMkbSnC9T",
"dateCreated": "2013-09-02 12:29:24"
}
],
"attachments": [this array excludes Google Drive attachments
{
"contentType": "application/octet-stream",
"version": 1,
"parentId": 2067818, task ID that the file is attached to
"description": "",
"apiId": "IEAAAEDYIYAB7DLK", Attachment UID that is used to match the file in the /attachments/ folder of the backup
"attachType": "External",
"id": 2067818,
"name": "test+doc+box.webdoc",
"dateUploaded": "2013-04-29 04:48:34"
}
],
"googleDocs": [
{
"resourceId":"1NPu0BlX9hrnSZf1OYh9TyFDoJWEYWxXiC2c01m6PnuY",ID of the file in Google
"id":2000736,
"name":"test document.doc",
"dateUploaded":"2014-09-02 19:56:43"
}
]
}
]
teams.json
teams.json - JSON array of user groups in the account
[
{
"uid": "G~0bzLlmeRUR",
"name": "Group name",
"Members": ["U2CBMkbSnC9T","rk7NvZyWoWbg"] array of UIDs of user who are members of the group
}
]
Enterprise account owners and admins with the right to “Export account data” can include BI export data in the backup.
BI Export lets you export your account’s data for future import to third-party analytics tools. To include it in the backup:
BI export data will be included to the backup when it's performed by any admin with the rights to both "Export account data" and "Configure Account Settings".