Some operations require the previous execution of other operations. For example, migrating an entry requires that you have already migrated the folder. As another example, a workflow process requires that you have already migrated user and group names, so that these names can be applied to its access control.
Here are notes regarding the sequence of operations:
Migrate users and groups, and create personal workspaces early in the process.
Use LDAP to establish the Forum users in Kablink Teaming.
You need the existence of personal workspaces to be able to migrate sub-workspaces and child folders. Also, migrating workflow and some types of custom commands requires that your users be established in Kablink Teaming first.
The Forum term “custom command” maps to “custom view and form” in Kablink Teaming.
Generally, migrate parents before children you wish to create.
Examples include migrating parent workspaces before its child folders, and migrating entries before migrating attached files.
Using SiteScape Forum, a “forum” maps to a “folder” in Kablink Teaming, a “reply” maps to a “comment” in Kablink Teaming, and the process of “attaching a file” maps to the Web services phrase “adding a folder file.”
Migrate binders before setting their ownership, team members, and access control.
The Forum items “workspaces and folders” map to the Kablink Teaming Web services term of “binders.” The Forum term “access control” maps to “membership.” Also, the Web services term “function” is equivalent to the term “roles” in the UI for Kablink Teaming.
Migrate custom commands before creating entries.
The custom command migration process cannot be done using only Web services (see Section C.5, Migrating Custom Commands and Workflow, for more information).
Migrate workflow processes before migrating entries.
First, the workflow-migration process cannot be done using only Web services (see Section C.5, Migrating Custom Commands and Workflow, for more information). Second, any entry that is currently in a workflow state requires the presence of the workflow definition in Kablink Teaming.
After migrating custom commands and workflow, you can migrate workflow associations for specific folders.
Finalizing operations include indexing folders and synchronizing any mirrored folders that you created.
Remember that migrated entries do not appear in the UI until you index the folders containing these entries.
The Kablink Teaming UI does not begin to mirror the files on the drive until someone manually synchronizes them. The Web services call is equivalent to a manual synchronization in the UI.