Language availability

   

Track-It! 2020 Release 02 online technical documentation is also available in the following languages:

  • French
  • German
  • Portuguese (Brazil)
  • Spanish
  • Spanish (XL)

The displayed language depends on your browser language. However, you can change languages from the Language menu.

Data that you can migrate

This topic describes the types of data that you can migrate using the Migration Tool.

Running the migration multiple times does not duplicate the data. Each time you run the Migration Tool, it looks for any new records in Track-It! 11.4 and migrates only the new data to Track-It! 20xx (for example, new tickets, ticket notes, and assignments).

For individual log files, the migration details for each data type is located in the Log folder of the location where you have extracted the Migration Tool.

You can migrate the following data by using the Migration Tool:

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

DataMapping considerations
Technicians
  • The Administrator technician in Track-It! 11.4 is not migrated because Track-It! 20xx has an out-of-the-box administrator technician.
  • The technicians migrated from Track-It! 11.4 to Track-It! 20xx are assigned a concurrent license. You can change the license assigned to technicians manually after the migration is complete.
  • In Track-It! 20xx, the technician with the Security Policy (permission set in Track-It! 11.4) as System Default admin in Track-It! 11.4 is assigned the system administrator permission.
  • In Track-It! 20xx, all technicians migrated from Track-It! 11.4 are migrated to the Help Desk group. After migration, you can move the technicians to the desired groups.
  • If a technician was not assigned a license in Track-It! 11.4, the technician is migrated as inactive in Track-It! 20xx.
  • In Track-It! 20xx, the value of Full Name field in Track-It! 11.4 is split as First Name and Last Name. If Last name is null, the Migration Tool inserts the <Enter Last Name> text in this field.
  • (2020 Release 02) Technician data present in ticket or assignment that does not match any technician's name in Technician lookup is migrated. The Migration Tool creates the login of such technicians and is a combination of <first Letter of technician First Name> + <Last Name>. A sequence is appended to the technicians if the login name matches an existing technician. These technicians are migrated as inactive technicians and details about them are stored in the log file.
  • (2020 Release 02) If a technician has a Login ID in Track-It! 11.4, the Login ID is migrated to Track-It! 20xx.
  • (2020 Release 02) A duplicate Login ID is migrated with its sequence added to the Login ID.

    Example

    Assume that LoginID1 is a duplicate for TechID. After migration, the new login ID is LoginID1 + TechID.

  • If a technician does not have a Login ID in Track-It! 11.4, after migration, the Migration Tool creates a Login ID. This Login ID is a combination of the <first letter of the technician First Name> + <Last Name> + <ID> with a maximum length of 30 characters. These technicians are migrated as inactive in Track-It! 20xx. To populate technicians in menus, the system administrator must mark them as active. If the Last Name does not contain a value, the Migration Tool creates a Login ID as <First Name> + <ID>. The ID is a unique value assigned to a user in Technician table in Track-It! 11.4.
  • The Migration Tool creates a database user login for each technician. For more information, see Creating and managing technicians.
  • While migrating, if Migration Tool is not able to create a Login ID for a technician, the technician information and the reasons for migration failure are recorded in the Technician log file.
  • In Track-It! 11.4, if the same Windows User ID is assigned to more than one technician, after migration, the User ID is mapped to only one technician in Track-It! 20xx. The priority is given to the technician with Windows Login enabled. The other technician information is maintained in a log file. If the windows authentication is disabled for all technicians, the Windows User ID is assigned to technician whose name appears first in the Technician table.
  • To support multi-domain technicians, the Migration Tool creates a technician as <NAME>@<Domain>.
  • If the NTAccount or SID is null, the user is migrated as a normal Technician. Disable Windows Auth for these records.
  • (2020 Release 02) A duplicate NTAccount is migrated with its sequence added to the NTAccount.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other technician records.
Work Order Status
  • If a value in the Work Order Status table is blank in the Track-It! 11.4 database, the migration process fails and the following error message is displayed:
    One or more WorkOrder Status with Empty value is detected. Please correct the WorkOrder Status which has Empty value and re-run the Migration Tool.
  • The following statuses are not migrated from Track-It! 11.4:
    • New
    • Open
    • Closed
    Track-It! 20xx contains two out-of-the-box statuses: Open and Closed. The records in Track-It! 11.4 are mapped to the corresponding status in Track-It! 20xx.
  • If one or more statuses have the same description, only one status is migrated based on the Status ID that appears first in the Status table.
  • If a work order status does not have a system type (Open or Closed), the records are migrated with Status Type = O.
  • (2020 Release 02) A NULL status in Track-It! 11.4 is not migrated to Track-It! 20xx. The information about these statuses is logged in the log file.
  • (2020 Release 02) The unique value for duplicate status is migrated to Track-It! 20xx after adding the suffix _sequence.
  • (2020 Release 02) A ticket or assignment with no matching status is migrated with the default Closed status to Track-It! 20xx. The information about these statuses is logged in log file.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other status records.
Priorities
  • Each migrated priority in Track-It! 20xx inherits the database server time zone.
  • If the Priority field of records does not contain a value in Track-It! 11.4, the information about these records is stored in the priority logs.
  • (2020 Release 02) If a Priority in ticket, assignment, or template is missing in the priority lookup table, it is created as inactive priority in Track-It! 20xx. The information about these priorities is logged in log files.
Categories
  • The values of the Type, Subtype, and Category fields in Track-It! 11.4 are migrated as Categories to Track-It! 20xx.
  • When you migrate, the hierarchy for Type, Subtype, and Category is maintained. The hierarchy is stored in the Category Full Path field in the Ticket and Assignment form as static text for Category in Track-It! 20xx.
  • If the Type, Subtype, and Category do not contain a value, the Migration Tool does not migrate the attributes or its children. This information is stored in the category log.
  • (2020 Release 02) If a Category in ticket, assignment, or template is missing in the category lookup table, it is created as inactive category in Track-It! 20xx. The information about these categories is logged in log files.
Tickets and Assignments
  • The Migration Tool maps the work order in Track-It! 11.4 to TI11_WOID field in Track-It! 20xx. This field is used to maintain the hierarchy of Ticket and Assignment in Track-It! 20xx.
  • The Migration Tool imports the work order with Work Order Type ID = 0 in Track-It! 11.4 as a ticket in Track-It! 20xx.
  • The Migration Tool imports the work order with Work Order Type ID = 1 in Track-It! 11.4 as an assignment in Track-It! 20xx.
  • The Migration Tool suffixes the summary of work order with [TI11 ID <WOID> ] in the Description field of a record in Track-It! 20xx.
  • Track-It! 11.4 has the Type, Subtype, and Category fields but the current release has the Category field only. After migration, the lowest value in the hierarchy in Track-It! 11.4 is mapped to the Category field in Track-It! 20xx.

    Example

    For example, Track-It! 11.4 contained the following hierarchy:

    • Type: Applications
      • Subtype: Email Application
        • Category: Office 365
      In this case, Office 365 is the value mapped to the Category field in Track-It! 20xx because it is the lowest in the hierarchy.
  • If a value for any of the following fields is deleted from the work orders in Track-It! 11.4, the corresponding value in Track-It! 20xx is displayed as null:
    • Category
    • Department
    • Priority
    • Location
    • Requestor
    • Technician
    • Technician Open By
    • Technician Assigned To
    • Technician Responded By
    • HelpDesk Lookup
    The Migration Tool stores these values from Track-It! 11.4 in Additional Information field of a record in Track-It! 20xx.
  • Currently, the following fields are not migrated to Track-It! 20xx:
    • SLA Policy
    • Asset ID
    • Change Request
    The Migration Tool stores the value of the above fields in Additional Information field of a record in Track-It! 20xx.
  • Tickets that are linked to open change requests are not migrated. The Ticket ID of the tickets that are no migrated by the Migration Tool are stored in the Ticket.log file.
  • The Migration Tool maps Notify_Cc and Notify_Bcc field from Track-It! 11.4 to the NotificationCcAddress and NotificationBccAddress fields in Track-It! 20xx.
Activity Codes
  • Only the activity codes that contain a value and have a valid description are migrated to Track-It! 20xx.
    (2020 Release 02) A blank or duplicate Activity Code in Track-It! 11.4 is not migrated to Track-It! 20xx. The information of these activity codes is logged in log file.
  • The description of a record is copied to the Code and Description of fields of an activity code in Track-It! 20xx.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other activity code records.
Task Notes
  • The Migration Tool maps the Note ID of work order or assignment notes in Track-It! 11.4 to the TI11_NoteID field in Track-It! 20xx.
  • The Migration Tool maps the note type as follows:
    • Incident Description as Ticket Description
    • Resolution as Ticket Resolution
    • Technician as Technician Note
    • E-mail Message as System Note
  • If a note does not contain an activity code, the Note Type = System Note and the Activity Code = Additional Informationis added in Track-It! 20xx.
  • (2020 Release 02) If a note has an activity code which does not exist in Activity Code Configuration data, the note is migrated with Activity Code = Additional Information.
  • Note the following considerations about the Created By field:

    Note

    The following considerations are also applicable for notes that are created by Email or Email Monitor settings.

    • If the Created By field is not mapped to a technician or a requestor and contains the System string, the value of the Technician field for a note is set as System Account in Track-It! 20xx.
    • If the Created By field is any requestor in Track-It! 11.4, the value of the Technician field is set as Self Service in Track-It! 20xx.
    • If the Created By field is mapped to a user who created the notes but is now deleted or modified, after migration, the value of the Technician field is null.
    • If any of the above points are not applicable, the value of the Technician field is migrated as null in Track-It! 20xx.

Requestors
  • Permission to access to Self Service for requestors in Track-It! 20xx is mapped same as in Track-It! 11.4.
  • The Full Name field in Track-It! 11.4 is split into the First Name and Last Name fields in Track-It! 20xx. If the value of the Last Name field is empty, the Migration Tool inserts the text <Enter Last Name> in the field.

    Note

    (2020 Release 02) A requestor with a duplicate or blank name in Track-It! 11.4 is not migrated.

  • If a requestor does not have a Login ID in Track-It! 11.4, after migration, the Migration Tool creates a Login ID by using the first letter of <first letter of the First Name> + <Last Name> + <UserID>. If the Last Name field is empty, the Migration Tool creates a login ID by using the <First Name> + <User ID>. The length of the Login ID must not exceed 30 characters. After migration, the requestors do not have access to Self Service. The system administrators must grant them the access.
  • If the Migration Tool cannot create a Login ID, the information about these requestors is stored in the Requestors log with the reason of migration failure.
  • (2020 Release 02) If a requestor has a Login ID in Track-It! 11.4, the Login ID is migrated to Track-It! 20xx.
  • (2020 Release 02) A duplicate Login ID is migrated with its sequence added to the Login ID.

    Example

    Assume that LoginID1 is a duplicate for ReqID. After migration, the new login ID is LoginID1 + ReqID.

  • In Track-It! 11.4, if the same Windows User ID is assigned to more than one requestor, after migration, the User ID is mapped to only one requestor in Track-It! 20xx. The priority is given to the requestor with access to Self Service. The other requestor information is maintained in a log file.
  • If the value of the Location or Department field for a requestor is deleted or renamed in Track-It! 11.4, the Migration Tool adds a null value for these fields in Track-It! 20xx. The modified value is added to the Additional Comments field in Track-It! 20xx.
  • If the requestor information contains an Employee ID in Track-It! 11.4, this information is migrated to the Additional Comments field of Requestor form in Track-It! 20xx.
  • (2020 Release 02) The Migration Tool migrates requestor records that were used in the following modules but were deleted from the requestor lookups (orphaned requestor records):
    • Orphaned requestor records used in Ticket, Assignment, and Purchase records as a Requestor
    • Orphaned requestor records used in Department record as a Department Head
    • Orphaned requestor records used in Change Request record as an Approver
    The orphaned requestor records are migrated as inactive records.
  • To support multi-domain requestors, the Migration Tool creates a requestor as <NAME>@<Domain>.
  • If the NTAccount or SID is null, the user is migrated as a normal Technician. Disable Windows Auth for these records.
  • Warning messages for requestor migration issues have been discontinued.
  • (2020 Release 02) A requestor with duplicate NTAccount is migrated with its sequence added to the NTAccount.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other requestor records.
Locations
  • If the value of the Location field in Track-It! 11.4 is null or duplicate, the Migration Tool does not migrate that value.
  • Information for null, duplicate, or missing location is stored in the Location log.
  • (2020 Release 02) If a Location in ticket, assignment, template, asset, requestor, or department is missing in the location lookup table, it is created as inactive location in Track-It! 20xx. The information about these locations is logged in log files.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors in the location log files and proceeds with migrating other location records.
Departments
  • The Migration Tool migrates Department before the Requestors.
  • After the Migration Tool migrates the Requestors, the Department Manager field in the Department is populated.
  • If the value of the Department field in Track-It! 11.4 is null, the information is stored in the Department log.
  • If the location in the Department is either deleted or renamed in Track-It! 11.4, the Migration Tool enters a null value in the Location of that Department in Track-It! 20xx.
  • (2020 Release 02) If the value of the Department field in Track-It! 11.4 is null or if it is a duplicate, the Migration Tool does not migrate it.
  • (2020 Release 02) If a Department in ticket, assignment, or template is missing in the department lookup table, it is created as inactive department in Track-It! 20xx. The information about these departments is logged in log files.
Attachments
  • The Migration Tool migrates only those attachments that are linked to a solution, asset, purchase order, work order, work order template, or assignment in Track-It! 11.4.

  • The Migration Tool migrates attachments that are less than 29 MB from Track-It! 11.4 to Track-It! 20xx. This is because Track-It! 20xx has a limit of 29 MB per attachment.
  • If any attachment is not migrated, the information about the attachment is stored in the Attachments log.
  • In Track-It! 20xx, the attachment information is stored in the FILEBLOB field of the Attachment table in the database as compared to the File System field in Track-It! 11.4.
  • If an attachment information is included in the File Information field in the database, but the file is not found in the File System field of the Attachment table, only the file information is migrated to Track-It! 20xx and a null value is inserted in the FILEBLOB field in the database.
  • (2020 Release 02) The Migration Tool moves all attachment data to the FILEBLOB2 column of the Attachment table.
Topics
  • The Migration Tool maps the KB_TYPEID field of a topic in Track-It! 11.4 to the TI11_TOPICID field of Track-It! 20xx. This helps to maintain the topic hierarchy in Track-It! 20xx.
  • (2020 Release 02) If the value of the Topic field is blank in Track-It! 11.4, the topic information is not migrated to Track-It! 20xx. The information of these blank topics is stored in the Topiclog after migration.
  • (2020 Release 02) A duplicate topic is migrated from Track-It! 11.4 to Track-It! 20xx.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other topics.
Solutions
  • The Migration Tool maps the SOLUTIONID field of a solution in Track-It! 11.4 to the TI11_TOPICID field of Track-It! 20xx. This helps to maintain the solution hierarchy in Track-It! 20xx.
  • The Migration Tool prefixes the summary of a solution with [TI11 ID <SOLUTIONID>].
  • If the summary of a solution is blank in Track-It! 11.4, the solution is not migrated and the information about such solutions is maintained in the Solution log.
  • (2020 Release 02) By default, if a solution record has topic that does not exist in Track-It! 11.4, the solution is migrated under General topic in Track-It! 20xx. However, if the General topic does not exist, the solution is migrated at root level.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other solution records.
Work Order Audit Trails
  • All work order or assignment audit trail in Track-It! 11.4 is migrated as a single System Note in Track-It! 20xx.
  • The audit trail related to notes are grouped by the timestamp and Created By before migration and a single note is added for each group. The Migration Tool prefixes the system notes with Note [<Note Id>] Added/Updated text.
  • The description of an activity code for the system notes that are related to the audit trail are migrated as Audit Trail imported from Track-It! 11.
  • Note the following considerations about the Technician field.

    Note

    The following considerations are also applicable for audit trails that are created by Email or Email Monitor settings.

  • If an audit trail is created because of a change by a user (requestor or a technician) who is not mapped to any migrated user, and the audit trail contains a system string, the value of the Technician field is set as System Account in Track-It! 20xx.
  • If the audit trail is created because of a change by a requestor in Track-It! 11.4, the value of the Technician field is set as Self Service in Track-It! 20xx.
  • If any of the above points are not applicable, the value of the Technician field is migrated as null in Track-It! 20xx.
  • If the audit trail is created by a user who is deleted or modified, after migration, the value of the Technician field remains null.

Help Desk Lookups
  • Each Help Desk Lookup in Track-It! 11.4 is copied or mapped to both a Ticket Lookup or an Assignment Lookup in Track-It! 20xx.
  • If a lookup value is null or empty in Track-It! 11.4, the Migration Tool does not migrate a lookup. The information about the lookups that are not migrated is stored in the Lookup log.
  • If the number of values added to the lookup is 100 or more (total length more than 2,000) in Track-It! 11.4, the migration stops and the following error message is displayed:
    Data truncation error
    This issue occurs because of the restriction of 2,000 characters for the SMTYPE field in the SMYSYBASEVIEDATA table where the lookup values are stored in Track-It! 20xx. In Track-It! 11.4, the lookup values are stored in a different table.
  • (2020 Release 02) When migrating custom lookups, the Migration Tool checks Total lookup character count which is equal to Character count of lookups in Lookup table + Character count of lookups in Tasks table missing in Lookup table.
  • (2020 Release 02) If the Total lookup character count is less than 4,000 (limit on Lookup field in Track-It! 20xx), Total lookups are migrated. If the Total lookup character count is more than 4,000, only ticket and assignment lookups are migrated. Lookups present in the Lookup table that are not migrated are logged in the log file.
  • (2020 Release 02) If a Help Desk Lookup in ticket, assignment, or template is missing in the help desk lookup table, it is created in Track-It! 20xx. The information about these help desk lookup is logged in log files.
Work Order Templates
  • The Migration Tool does not migrate templates with the name longer than 150 characters. Information about the templates that are not migrated is stored in the Templates log.
  • The Migration Tool does not migrate templates that have a null value for the Template Name field.
  • (2020 Release 02) Templates with a duplicate name in Track-It! 11.4 are migrated with Template Sequence appended to their name. This information is logged in the log file.
  • If a Work Order template is not migrated, the linked Assignment templates are also not migrated.
  • The Migration Tool maps the WOID of a Work Order or an Assignment template in Track-It! 11.4 to the TI11_WOID field in Track-It! 20xx. This helps to maintain the hierarchy of the Ticket and Assignment templates in Track-It! 20xx.
  • The Work Order Template in Track-It! 11.4 contains Type, Subtype, and Category fields. In Track-It! 20xx, the Template form contains only the Category field. The Migration Tool maps the lowest member of the hierarchy (Type, Subtype, and Category) in Track-It! 11.4 to the Category field of a Ticket template in Track-It! 20xx. The hierarchy information is also stored in the Category Full Path field of a template in Track-It! 20xx.
  • If the value of any of the following fields in Track-It! 11.4 template is not migrated, that field is not added in Track-It! 20xx template:
    • Category
    • Department
    • Help Desk Lookup
    • Location
    • Priority
    • Requestor
    The values of these fields are added to the Additional Information field of a template in Track-It! 20xx. Information about these template fields is logged in the log file.
  • Currently, the Migration Tool does not migrate the values of the Cc and the Bcc field from Track-It! 11.4 to Track-It! 20xx. The values of these fields are added to the Additional Information field of a template in Track-It! 20xx.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other templates.
Network Lookups
  • Network Lookups are considered as configuration items.
  • The Migration Tool does not have an option to select Network Lookups for migration. Network Lookups are migrated by default along with the assets.
  • The Migration Tool maps the Network field in Track-It! 11.4 to the SMTYPE field in Track-It! 20xx.
  • If a Network lookup value is null in Track-It! 11.4, the Migration Tool does not migrate the lookup. The information about the lookups that are not migrated is stored in the Network Lookups log.

  • Duplicate Network Lookup values are removed.
  • If the number of Network Lookup values for a single Asset Lookup is 100 or more (total length more than 2,000), the migration process stops and the following error message is displayed:
    Data truncation error
    This issue occurs because of the restriction of 2,000 characters for the SMTYPE field in the SMYSYBASEVIEDATA table where the lookup values are stored in Track-It! 20xx. In Track-It! 11.4, the lookup values are stored in a different table.

Vendors
  • Vendor is considered as configuration item.
  • The Migration Tool does not have an option to select Vendor for migration. Vendors are migrated by default along with the assets.
  • If a vendor value is null in Track-It! 11.4, the Migration Tool does not migrate the vendor. The information about the vendors that are not migrated is stored in the Vendor log file.
  • Duplicate vendor values are removed.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other vendor records.
Tracked Items
  • The Migration Tool maps the Asset Number of WORKSTAT from Track-It! 11.4 to TI11_Parent field of Track-It! 20xx and is used to maintain the hierarchy of assets and tracked items.
  • The Migration Tool migrates the tracked items as assets in BCM. There is no separate table or view for tracked items in Track-It! 20xx.
  • The Migration Tool first creates the tracked item in BCM with the help of API which returns BCM Asset ID. This Asset ID is used to migrate the tracked item to Track-It! 20xx.
  • Any tracked item that is not migrated in BCM, will not be migrated to Track-It! 20xx. The migration process continues even if any tracked item fails to migrate to BCM. The information about the tracked items that are not migrated is stored in the log file with the error messages returned by the BCM API.
  • The Migration Tool creates the tracked Item as ProductName_ItemID in Track-It! 20xx.
  • The Migration Tool does not migrate deleted tracked items in BCM and Track-It! 20xx.
  • A duplicate tracked item that is not allowed by the BCM API is not migrated in Track-It! 20xx.
  • The Migration Tool imports the tracked item with the value of the Product Type field set as Other in Track-It! 20xx.
  • The Migration Tool maps the installed date of the tracked item to the BCM Service Start date.
  • The Migration Tool adds the information about the Product Type, Part number, Maintenance Warranty, Tracked Item Comment, Master Item Comment, Master Support, Reference number, Lease expiration date, Lease Number, Installed By, and Date Installed and a note in Track-It! 11.4 to the Additional Information field of Track-It! 20xx.

Notes

  • The Migration Tool first migrates the asset followed by the tracked item and then the relation between the asset and the tracked item. The Migration Tool does not migrate the tracked item if the parent asset is not migrated.
  • If the BCM Master asset is present in Track-It! 11.4 database, the Migration Tool does not migrate the Master asset and its relation with other modules to Track-It! 20xx.
Assets
  • The Migration Tool maps the Asset Number of WORKSTAT from Track-It! 11.4 to the TI11_Inventory field of Track-It! 20xx. This field is used to retain the asset and tracked item hierarchy in Track-It! 20xx.
  • The Migration Tool first creates an asset in the BMC Client Management (BCM) with the help of API which returns the BCM Asset ID. This Asset ID is used to migrate the asset in Track-It! 20xx.
  • Any asset that is not migrated in BCM, will not be migrated to Track-It! 20xx. The migration process continues even if any asset fails to migrate in BCM. The information about the assets that are not migrated is stored in the log file with the error message returned by the BCM API.
  • (2020 Release 02) If the Asset Type value is blank in Track-It! 11.4, it is not migrated to Track-It! 20xx. The information about such asset types is logged in the Log file.
  • If the Asset Name field value is null in Track-It! 11.4, the Migration Tool creates an asset based on the Asset ID field value in Track-It! 20xx.
  • A duplicate asset that is not allowed by the BCM API is not migrated to Track-It! 20xx.
  • (2020 Release 02) A duplicate Asset Type under the same parent is not migrated. The information about such Asset Types is logged in the Log file.
  • The Migration Tool imports an asset with the value of the Asset Type field set to Other in Track-It! 20xx.
  • The Migration Tool adds the information about the Asset Type, manually updated Asset Name, Asset ID and a note in the Track-It! 11.4 to the Additional Information field of Track-It! 20xx.
  • The Migration Tool maps the ASSETYPEID and ASW_NUM (ID) field from Track-It! 11.4 to the new field ITASSET_TYPE and COMPANY_ASSET_ID in Track-It! 20xx.
  • The Migration Tool migrates assets with limited details about both hardware and software. However, after the initial migration, you can obtain more details about asset hardware and software by configuring Track-It! 20xx for discovery and re-running the Migration Tool, which refreshes and updates the asset data.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other Asset Types.

Best practice

We recommend that you rediscover the migrated assets after configuring Track-It! 20xx to make sure that the asset migration contains the most accurate and latest details for all of your assets.
Change Requests
  • Change management includes tickets and the change requests linked to them.
  • The Migration Tool maps the ChangeRequestID of a change request in Track-It! 11.4 to TI11_CHANGEID field in Track-It! 20xx. This field is used to cause the hierarchy of change request and change approval in Track-It! 20xx to persist.
  • The Migration Tool migrates only the change requests that are completed.
  • If an approver or a technician (Open By, Assigned To) referenced in any existing change requests is deleted in Track-It! 11.4, then the corresponding field values in Track-It! 20xx will have null values.
  • The value of the Policy Name field in Track-It! 11.4 is stored in the Additional Information field of a change request in Track-It! 20xx.
Change approvals
  • The Migration Tool maps the DecisionID of decision (approval record) from Track-It! 11.4 to the TI11_CHANGEAPPRID field in Track-It! 20xx. This field is used to cause the hierarchy of change approval and change approval review history in Track-It! 20xx to persist.
  • The Migration Tool migrates only the approval records that are linked to the successfully migrated change requests.
  • All the approvals in Track-It! 11.4 are migrated as stage 1 approvals in Track-It! 20xx.
  • All approval records that are in the Pending approval(Evaluating) status in Track-It! 11.4 are migrated as No Action Required status in Track-It! 20xx.
Change Approval reviews
  • The Migration Tool migrates only the approval notes that are linked to the successfully migrated approval record in Track-It! 20xx.
  • A note added from Self Service in Track-It! 11.4 is migrated with the Note by the Requestor activity code. For this note, the technician is assigned as Self Service in Track-It! 20xx and the requestor is the user who has added the note.
  • A note added from the Technician portal as a response to a change request is migrated with the Note by Technician activity code. For this note, the technician is assigned as the user who added the note.
  • A note added by an approver via an email message is migrated with the Email received activity code. For this note, the requestor is assigned based on the email address.
  • If the requestor detail for a note is not found in Track-It! 11.4, the Requestor field is left blank in Track-It! 20xx. The note is appended by the name of the requestor who created the record.
  • If the technician detail for a note is not found in Track-It! 11.4, the Technician field is populated with the SYSTEMACCOUNT technician. The note is appended by the name of the technician who created the record.
  • If a reviewer is reassigned, the Migration Tool adds a note in the Details section of a change request instead of the change approval. The activity code for this note is Approver Changed.
Purchasing configuration
  • The Migration Tool migrates Ship to, Bill to, and Tax Rate from Track-It! 11.4 to Track-It! 20xx.
  • The Migration Tool does not migrate the Enable Auto-increment of purchase order numbers setting to Track-It! 20xx.
  • The Migration Tool migrates the setting for Enable tax calculations on shipping charges from and reproduces the same setting for each migrated purchase order in Track-It! 20xx.
Product type
  • The Migration Tool merges Product Type and Asset Type in Track-It! 11.4 and maps them into TIAsset Type in Track-It! 20xx.
  • The Migration Tool maps AssetTypeId of IN_AssetType from Track-It! 11.4 to the TI11_TIASSETTYPEID field in Track-It! 20xx. The migrated data maintains the Asset type Sequence of Track-It! 11.4.
  • The Migration Tool maps ID of PRODTYPE from Track-It! 11.4 to the TI11_TIASSETTYPEID field of Track-It! 20xx. The migrated data maintains the Product type Sequence of Track-It! 11.4.
  • The Migration Tool migrates Asset Type first, and then migrates Product Type.
  • During migration and merging of Product Type and Asset Type from Track-It! 11.4 to the TI11_TIASSETTYPEID field of Track-It! 20xx, the suffix AT_ is appended for the Asset type sequence, and the suffix PT_ is appended for the product type sequence.
  • (2020 Release 02) If the Product Type is blank in Track-It! 11.4, it is not migrated to Track-It! 20xx. The information about such product types is logged in the Log file.
  • (2020 Release 02) A Product Type that is linked to a Tracked Item but does not exist is migrated as inactive product type. The links of such product types are displayed on the Asset Form.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other product types.
Master Item
  • The Migration Tool maps Master Item (PRODUCT) in Track-It! 11.4 to _MASTERITEM_ in Track-It! 20xx.
  • The Migration Tool maps PRODUCT_ID of PRODUCT in Track-It! 11.4 to the TI11_MASTERITEMID field in Track-It! 20xx. The migrated data maintains the Master Item Sequence of Track-It! 11.4.
  • (2020 Release 02) Master items that do not have a product name in Track-It! 11.4 are not migrated to Track-It! 20xx. These master items are logged in the log file.
  • (2020 Release 02) Master items with duplicate product name in Track-It! 11.4 are not migrated. The information about these master items is logged in the log file.
  • (2020 Release 02) Master items in Purchase Item records that are missing in Master Item lookup table are created as inactive master items in Track-It! 20xx. The information about these master items is logged in the log file.
  • (2020 Release 02) After migration to Track-It! 20xx, each invalid character (/, \, :, ", *, ?, <, >, and |) in the product name of the master item is replaced by underscore (_). The information about these master items is logged in the log file. If duplicate names still exist after replacing the invalid characters, the Product ID is appended to the product name. If the master item does not have a Product ID, the duplicates are ignored.
  • (2020 Release 02) Migration does not stop if there are errors. The Migration Tool logs the errors and proceeds with migrating other master items.

Purchase Item
  • The Migration Tool maps Purchase Item (POITEM) in Track-It! 11.4 to _POITEM_ in Track-It! 20xx.
  • The Migration Tool maps POITEM_ID of POITEM in Track-It! 11.4 to the TI11_POITEMID field of _POITEM_ in Track-It! 20xx. The migrated data maintains the Purchase Item Sequence of Track-It! 11.4.
  • During the migration of Purchase Items, the Migration Tool also migrates the relationships with Vendor, Master Item, Purchase Order, and so on.
Purchase Order
  • The Migration Tool maps Purchase Order (PURCHASE) in Track-It! 11.4 to _PO_ in Track_It! 20xx.
  • The Migration Tool maps ID of PURCHASE in Track-It! 11.4 to the TI11_PURCHASEORDERID field of _PO_ in Track-It! 20xx. The migrated data maintains the Purchase Order Sequence of Track-It! 11.4.
  • During migration, the Sales Tax is calculated and included in migrated Purchase Orders.
  • During migration, the tax calculation on shipping is calculated and included in migrated Purchase Orders based on the global setting Enable tax calculations on shipping charges in Track-It! 11.4.
  • The Migration Tool migrates the Status of the purchase order. If the Track-It! 11.4 purchase order contains a Received date, the migrated Purchase Order status is Closed. If the quantity of received Purchase Items is greater than zero, but less than the total quantity ordered, the migrated Purchase Order status is Partially Received. For all other conditions of the quantity of received items, the migrated Purchase Order status is Open.
  • The Migration Tool migrates all Purchase Order attachments in Track-It! 11.4 and includes them as attachments in the migrated Purchase Orders of Track-It! 20xx.
  • The Migration Tool migrates the shipping cost on Purchase Orders from Track-It 11.4 to Track-It! 20xx.

Was this page helpful? Yes No Submitting... Thank you

Comments