Migrated tools and assets

The following tools are typically migrated as complete systems:

  • Project management tools (such as Atlassian Jira)
  • Document management tools (such as Atlassian Confluence)
  • Binary repositories (such as Artifactory Pro or Sonatype Nexus)

Migration process overview

The migrations will be done based on the following high level flow:

  1. Collection of necessary source system information
  2. Source system analysis
  3. Preparations
  4. Test migration
  5. Customer testing and approval
  6. Production migration, including traffic redirection from the old system to new one (e.g. link references used in past emails and integrations with the rest of the legacy tool chain)

After the tool-by-tool migrations, the old tool instances are seamlessly replaced with new ones, and the project work can carry on normally.

Migration responsibilities


Phase

Responsible party

Collection of necessary source system information

Customer

Source system analysis

Eficode

Preparations

Eficode, Customer

Test migration

Eficode

Customer testing and approval

Customer

Production migration

Eficode

Migration sequences

Preparations

  1. Confirm that the migration project team is ready and available 
  2. Agree on a regular meeting schedule between all participants
  3. Prepare a data transfer location available for all participants (to fetch and push data)
  4. Lock down changes in the tools (such as plugins, configurations)
  5. Prepare XML exports to Eficode for the test migration 

Example: Atlassian Jira Migration

  1. Import the XML/database into test instance, create user lists and mappings
  2. Fix user mappings
  3. Check data validity
  4. Prepare for production deployment
  5. Customer QA 

Example: Atlassian Confluence Migration

  1. Import the XML/database into test instance, create user lists and mappings
  2. Fix user mappings
  3. Check data validity
  4. Prepare for production deployment
  5. Customer QA