Migration options
Before you migrate to a newer version of FootPrints, based on your requirements, you must choose an option that best suits your organization.
The following topics helps you to choose the suitable migration option:
- Migration options
- Details of Migration options
- Option 1.1 - No migration; version 11 and version 12 simultaneously
- Option 1.2 - No migration; export ticket data from version 11 to version 12
- Option 2.1 - Migrate configuration settings only
- Option 2.2 - Migrate only configuration settings and export ticket data
- Option 3.0 - Migrate configuration settings and data
- Related topics
Migration options
The following migration options are available:
Migration options | Run Migration Advisor? | Migrate only configuration? | Migrate ticket data? | Export import ticket data | Run both old and new systems side-by-side? |
|---|---|---|---|---|---|
Option 1.1 - No migration; version 11 and version 12 simultaneously | ✅️ | ❌️ | ❌️ | ❌️ | ✅️ |
Option 1.2 - No migration; export ticket data from version 11 to version 12 | ✅️ | ❌️ | ❌️ | ✅️ | ❌️ |
Option 2.1 - Migrate configuration settings only | ✅️ | ✅️ | ❌️ | ❌️ | ✅️ |
Option 2.2 - Migrate only configuration settings and export ticket data | ✅️ | ✅️ | ❌️ | ✅️ | ❌️ |
Option 3.0 - Migrate configuration settings and data | ✅️ | ✅️ | ✅️ | ❌️ | ❌️ |
Details of Migration options
Refer to the following table for more information about the migration options:
Option 1.1 - No migration; version 11 and version 12 simultaneously
Description
This option does not involve migration and requires you to run both version 11 and version 12 systems simultaneously.
This scenario would suit you, if you:
- Want to use the new and improved configuration capabilities to better tailor FootPrints to your business as it is today
- Would like to utilize Information Technology Infrastructure Library (ITIL) based service desk templates
- Want to take immediately take advantage of the of new features offered in FootPrints version 12
Process flow
Advantages
- Timeline to go live on FootPrints version 12 system that is not on a critical path
- Do not have to sync data for both versions
- Take advantage of FootPrints version 12 functionality when you do not migrate FootPrints version 11 configuration
Considerations
- Agents have to maintain two FootPrints systems at the same time
- Customers may have service requests in two systems
- May have to temporarily manage two CMDBs
- May need to keep older version system running to provide historical reference
- Migration Advisor report does not include information about configurations and data
Option 1.2 - No migration; export ticket data from version 11 to version 12
Description
This option does not involve migration and exports only ticket data from version 11 to version 12 systems.
This scenario would suit you if you:
- Want to use the new and improved configuration capabilities to better tailor FootPrints to your business as it is today
- Would like to utilize Information Technology Infrastructure Library (ITIL) based service desk templates
- Want to take immediately take advantage of the of new features offered in FootPrints version 12
Process Flow
Advantages
- One required one system to be maintained
- Can manage only one view for customers
- Adapt the FootPrints version 11 hardware
- Can evaluate the ticket data and eliminate the data that is not required for FootPrints version 12
Considerations
- Temporarily maintain two CMDBs
- Provide training to users
- Migration Advisor report does not include information about configurations and data
- Export and import of ticket data loses ticket history
Option 2.1 - Migrate configuration settings only
Description
This option migrates only the configuration data and requires you to run both version 11 and version 12 systems simultaneously.
This scenario would suit you if you:
- Like how FootPrints is working for you now but have several ideas for improvements
- Would like to evolve the customer and agent experience
- Want to experiment with the new features offered in FootPrints version 12 to determine which best benefits your requirements
Process flow
Advantages
- Timeline to go live on FootPrints not on a critical path
- Does not require to sync FootPrints version 12 and FootPrints version 11 data
Considerations
- Temporarily maintain two CMDBs
- Agents have to maintain two FootPrints systems at the same time
- Customers may have service requests in two systems
- May need to keep older version system running to provide historical reference
- Migration Advisor report does not include information about configurations and data
Option 2.2 - Migrate only configuration settings and export ticket data
Description
This option involves only migrating configuration data and export the ticket data from version 11 to version 12 systems.
This scenario would suit you if you:
- Are satisfied with how your Workspaces and Address Books are configured
- Want to maintain historical data in your FootPrints version 12 instance
- Want to reexamine your CMDB to see how to take advantage of FootPrints version 12 capabilities
- Would like to evolve the customer and agent experience
Process flow
Advantages
- Agents have to work on one system only
- Able to manage only one view for customers even across imported tickets in one workspace and new tickets in another workspace
- Able to migrate configuration for current tickets and can also create a new workspace for new tickets
- Can evaluate ticket data in FootPrints version 11 and determine what is not required for importing into FootPrints version 12
Considerations
- Temporarily maintain two CMDBs
- Provide training to users
- Migration Advisor report provides value but will need to ignore extraneous information about configuration and data migration as the migration is not completed
- Configuration changes in FootPrints version 11 prior to go-live date may have to be duplicated in FootPrints version 12
- Migrating configuration carries forward few FootPrints version 11 limitations into FootPrints version 12
- Loss of ticket history after export and import of ticket data
Option 3.0 - Migrate configuration settings and data
Description
This option involves migrating the configuration and other data and run both version 12 systems.
This scenario would suit you if you:
- Are satisfied with how your Workspaces and Address Books are configured
- Want to maintain historical data in your FootPrints version 12 instance
- Want to reexamine your CMDB to see how to take advantage of FootPrints version 12 capabilities
- Would like to evolve the customer and agent experience
Process flow
Advantages
- Agents have to work on one system only
- Able to manage only one view for customers even across imported tickets in one workspace and new tickets in another workspace
- Able to migrate configuration for current tickets and can also create a new workspace for new tickets
- Can evaluate ticket data in FootPrints version 11 and determine what is not required for importing into FootPrints version 12
Considerations
- Temporarily maintain two CMDBs
- Provide training to users
- Migration Advisor report provides value but will need to ignore extraneous information about configuration and data migration as the migration is not completed
- Configuration changes in FootPrints version 11 prior to go-live date may have to be duplicated in FootPrints version 12
- Migrating configuration carries forward few FootPrints version 11 limitations into FootPrints version 12
Related topics