Metadata file
Description: To perform the import, you need to have a meta-data.json file, which serves as the entry file. This JSON file should contain the entities to be imported and the relative paths to separate JSON files for each entity.
Fields:
| Field Name | Type | Required | Description |
|---|---|---|---|
| entities | array | Yes * | An array of entities to be mapped |
| entities_paths_map | object | Yes | Paths to JSON files which should be the source of import |
Description of fields:
entities:
An array of entities to be mapped. Available entities include boards*, columns*, columns_mapping, cards, comments, custom_fields, documents*, document_files, files, folders, properties_mapping, spaces, users
entities_paths_map:
Paths to JSON files that will be used as the source for import. The format of the file path is not strict, meaning it can be specified in various ways, such as: /<filename>.json, ./<filename>.json, <filename>.json
* - System allows: importing documents or importing boards and columns as a group (both must be included), or all content simultaneously. Read more about available importing options in 'Introduction' section.
JSON schema:
