Migration Assumptions

As you move onto CTF 17.1, you may want to know the assumptions that were made while migrating CollabNet Enterprise Edition (CEE) project information to CollabNet TeamForge 17.1 (CTF 17.1).

  • Global Data:
    • Default usergroups '*Domain Users' and '**Host Users' are not migrated.
    • System users, if part of any user group, are dropped.
    • System users like guest, webmaster, postmaster and mailer-domain are not migrated and their references are mapped to 'Nobody' user.
    • Host Superuser (root) is not migrated in favor of administrator account in CTF 17.1 and its references are mapped to the administrator user.
    • Users who are associated with Host Admin role are migrated as Site administrators.
    • Domain roles; 'Anonymous Guest' and 'Registered User' are dropped and their permissions are transferred to each public project's Default Access Permissions user class.
    • Host roles are not migrated.
    • Project announcements of www project are moved to the Look project as news.
    • CEE's HAC_AUDIT_LOG_ENTRY table is moved to cee_backedup_audit_log.
  • Projects Data:
    • Unapproved and deleted projects are not migrated.
    • Default projects like testproject, www, project-templates are not migrated.
    • Categories and project groups are migrated as normal projects.
    • License detail of projects is not migrated.
    • CVS repositories are accessible with a new URL only.
    • CVS working copies must be recreated.
    • SVN working copies continue to work as is.
    • The Alias URL of the project is not migrated.
    • When the project creation date is not found for a project in the audit log, the default fallback value (2000-01-01) is used.
    • Project owners message is moved to the news component as a news item.
  • Discussion services tool:
    • Soft deleted discussions are not migrated.
    • Trusted discussions are migrated as moderated discussion and trusted subscribers are moved to the trusted users list.
    • The following discussion settings are dropped as CTF 17.1 does not support these settings:
      • Web UI View
      • Web Posting
      • Web Post CAPTCHA
      • Display Email Address
      • Remove Deleted Messages
      • Remove Unmoderated Messages
      • Content in Email
      • Message Size
      • Attachments
      • Advanced Email Filters
    • The following discussion topic value is dropped as CTF 17.1 does not support it:
      • Message headers
    • In CTF 17.1, discussion email address must begin with an alphabet and it can not contain special characters except an underscore. So, if a CEE's discussion address contains hypens or periods, they are replaced with underscores. Also, if it begins with a number, it is replaced with the equivalent number in word followed by an underscore.
    • Lengthy discussion topic titles, if any, are truncated to 250 characters.
    • Soft deleted approved and unapproved topics including replies are not migrated.
  • Documents and files tool:
    • Unapproved folders and documents are not migrated.
    • In CTF 17.1, a document's status can be either draft or final. So, CEE's documents in 'Stable' status are migrated as final and documents in any other status are migrated as draft.
  • Announcements tool:
    • Announcements are migrated to the news component in CTF 17.1.
    • CEE features like Image url, publishing and event dates are not supported in CTF 17.1. Those details are appended as part of announcements itself.
  • Project pages tool:
    • The documents existing in CEE’s "Document" component are moved to a sub-folder in the CTF 17.1’s "Documents" tool’s "cee-migrated-docs" folder.
    • The page components, HTML and Activity table components are migrated as text/html component.
    • The page components Metrics report, Milestones table and Project overview are not migrated.
    • The availability property of a page 'All users' and 'Users with project-edit' is mapped to 'Visible'; and 'None' will be mapped to 'Hidden' in CTF 17.1.
    • Backward compatibility of free-form page references in html components is not supported.
    • Sub-page icons are not migrated.
  • Issue Tracker tool:
    • Issue tracker in CEE is migrated to a tracker called 'Issue tracker' in CTF 17.1.
    • Issues are migrated as artifacts.
    • The email notification preferences are not migrated.
    • The associations between Component and Subcomponent, Component and Version and, Component and Target Milestone are dropped as CTF 17.1 does not support these associations.
    • Issue tracking configuration parameters not migrated.
    • Internal users of Issue tracker are dropped.
    • Dependencies are migrated as associations.
Parent topic: Migrating tools from Enterprise Edition to TeamForge 17.1