Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

About converting projects

To current project customers

This document is only important if you use the old project functionality and need to convert to the new module.

As the new module behaves slightly differently, a conversion tool is needed.

The purpose of the tool is to move the old projects into the new module, while taking care of the differences the new module introduces.

All this while making sure that no downtime is experienced besides the time spent for the actual conversion, which will vary depending on the amount of projects. Estimated between 5-10 minutes.

The different steps

To make sure that the implementation of the new module is completed successfully, the conversion is done in these steps.

  1. Activate the module
  2. Setup the module
  3. Convert the projects

1. Activate the module

This is done by a Microbizz partner.

Once the module is activated, the following happens:

  • The new module is added to Microbizz
  • The old project functionality is removed and projects are hidden

It's therefore important to do this manoeuvre when the system is not being used. For example after work or in an agreed break.

2. Setup the module

Setting up the module is done by the customer (together with a Microbizz partner if needed).

First step is to head to the conversion tool page.

 

The following menu is shown, and the purpose of the tool is to:

  • Help the user understand what needs to be setup
  • Complete the actual conversion

Let's take a look at the different todos in the tool:

  • Setup project types: Project types are explained here
  • Check task filters: As the current task type called "project" will be replaced with the new project object, the old filters showing projects, will not work anymore. These should therefore be replaced with filters from the project module
  • Check import filters: As the current task type called "project" will be replaced with the new project object, the old import filters that are used to create/update projects, will not work anymore. These should therefore be replaced with import filters for the project module
  • Check export filters: As the current task type called "project" will be replaced with the new project object, the old export filters that are used to export project information, will not work anymore. These should therefore be replaced with export filters for the project module
  • Check update filters: As the current task type called "project" will be replaced with the new project object, the old update filters that are used to update projects, will not work anymore. These should therefore be replaced with update filters for the project module
  • Setup number series: If tasks number series is currently used to manage task/project numbers, a corresponding series can be setup for the project module. When converting the projects later, the current numbers will be transferred, so that the users can relate to the same numbers as they are used to
  • Setup permissions and policies: The new module contains it's own set of permissions and policies that should be adjusted according to the use
  • Check task templates: All task templated that are used to create projects in the task module, will be removed, and should therefore be replaced by templates that create projects from the new module


  • No labels