Importing a Document360 project ZIP file

Plans supporting import and export of project

Once you complete exporting Document360 ZIP files, they can be imported to any project. This is useful when you need to migrate your knowledge base from one project to another, or if you need to restore your knowledge base from a backup ZIP file.

Importing a Document360 ZIP file includes:

• Articles and category pages

• Media files included in the exported ZIP file

NOTE

To import a Document360 project, the team account must have the Editor content role. For custom content roles, the account must have Update and Publish access to the Project Import & Export feature.

Importing a project ZIP file

To import a Document360 project ZIP file,

1. Navigate to Documentation () > Content tools > Import and export > Import and export project in the Knowledge base portal.

2. Click the Import button to open the Import project panel.

3. Drag and drop the project ZIP file from your local storage or use the Upload option to select the ZIP file.

   Document360 will upload and validate the ZIP file.

4. If you need to choose a different ZIP file, click Replace.

5. After successful validation, a confirmation message will display details about the ZIP file, such as:

   • Languages

   • Number of categories

   • Number of articles

6. Select the Set article status to publish checkbox if you want all the imported articles to be published. If the checkbox is not marked, all the imported articles remain in the Draft state.

7. Click Import to finalize the process.

Once the ZIP file is successfully imported into your desired project, all articles and media files will become available within the project.    

Behavior of importing projects with the same workspace slug

When importing a project ZIP file into another project with the same workspace slug:

• The imported articles and categories will merge with the existing articles and categories within the same workspace.

If the workspace slug of the destination project differs from the slug in the imported ZIP file:

• A new workspace will be created with the workspace name and slug from the imported project. All imported data will be added to this new workspace.

How to import a project ZIP file into a specific workspace without overriding existing content?

To import a project ZIP file into a specific workspace while avoiding conflicts with existing articles or workspace slug:

1. Export the desired categories from your Document360 project as a ZIP file.

2. Extract the ZIP file in your local file explorer.

   The extracted folder contains two main directories: Media and workspace_slug.

   • Media: Contains all media files of the project.

   • workspace_slug: Contains two folders and a JSON file:
     a) Articles: List of articles in the project.
     b) Categories: List of page categories in the project.
     c) workspace_slug_category_articles: A source file with workspace and article data.

3. Open the workspace_slug_category_articles file in a code editor.

4. Modify the workspace name and slug to match the destination workspace name and slug.

5. Save your changes and rename the JSON file using the destination workspace slug format: workspace_slug_category_articles.

   Example: v2_category_articles

6. If needed, update the slugs of articles or categories, and the language code in the extracted folders.

7. Compress the modified files into a new ZIP file and name it using the destination workspace slug.

8. Return to your Document360 project and import the newly created ZIP file.

In this example, we are importing a project ZIP file with the workspace slug v1 into a project with the workspace slug v2. To match the target workspace v2, we update the workspace name and slug in the v1 ZIP file.

The above screen recording demonstrates how to change the workspace slug and name from v1 to v2 in the extracted files, re-compress the modified files into a new ZIP file, and successfully import them into the Document360 project with the workspace slug v2.