Migrating your content to TeamSite is easy

[ishanijerin1]

Considering the above, the flow of TeamSite content migration is as follows. Let's take a look at each step.

teamsite_flow.jpg



1. Creating a user group
Create users and groups that will use TeamSite. Users will be content creators, approvers, and TeamSite administrators. It is basic to use OS users, but it is also possible stockholder database to link external users such as LDAP. Groups are mainly used to group members such as approvers and to assign access permissions to each piece of content. You can use either OS groups or TeamSite groups. Using OS groups increases versatility, but we recommend using TeamSite groups if you want to prepare groups specifically for TeamSite.

2. Creating a branch work area
Create a branch and a work area in TeamSite. A branch is a framework for managing website content and related parties. Usually, one branch is created for each site. A work area is, as the name suggests, a work area where users edit content. Create one work area when sharing with multiple users, but you can also create multiple work areas when preparing a work area for each user. When migrating content, you may also create a work area as a temporary copy location.

3. First copy of content
To check whether the existing content can be used in the CMS before the production release, copy the content from the public server (the server that publishes the existing website on the Internet). As mentioned earlier, TeamSite can copy content with the site structure intact. For example, if the TeamSite server and the public server are both Linux, you can copy the content with a single rsync command.