Document360 — Migration Reference

Role in migrations

• Category (KB): supported as both (source and target).
• Folder (KB): supported as both (source and target).
• Article (KB): supported as both (source and target).

Field-level support migrating FROM Document360 (Article)

Field-level support migrating TO Document360 (Article)

Migration options available for Document360

• Migrate content translations - applies to: both (Article)
• Select records for Demo - applies to: source (Article)

Document360 — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/document-360-migration-guides/

How to Get the API Token for Migration?

1. Open Settings. Log in to your Document360 account and click on Settings.
2. In the settings menu, go to the API Tokens tab.
3. Click on Create API Token.
4. Configure the Token:
   1. Enter a name for the token (for example, ‘Main Token’).
   2. Enable the checkboxes for GET and POST methods to allow both > retrieving and importing data.
5. Once generated, copy the API token.
6. Add the Token to the Migration Wizard

Paste the copied token into the API Token field in the Migration Wizard to authorize the connection between Document360 and the migration tool.

Document360 Migration Specifics

1. Only the Knowledge Base is migrated.
2. Document360's structure is Project → Workspace → KB. A project is a broader entity that can contain multiple workspaces. When a client connects, only the workspaces belonging to the project they connected are available. Each project has its own separate API token.
3. Migration is performed from one workspace to one workspace.
4. On the source side, a three-level structure isn't mandatory — articles can belong directly to a category.