Precision Bridge Newsletter: Warm Days, Bright Ideas
As summer unfolds, we're sharing fresh insights, recent wins, and a few helpful resources to support your data migration and management initiatives. Whether you're tackling a transformation project or staying sharp on the latest trends, we hope this month’s update provides you with some new information to power your projects.
New Partner: Avante
We are pleased to announce the signing of a new partnership agreement with Avante.
Avante, a Premier Ivanti Partner and ITSM/ESM leader since 1999, delivers Precision Bridge solutions—streamlining data migration, archiving, and synchronization across Ivanti, Cherwell, and beyond to enable faster transitions, stronger compliance, and smarter service management transformation.
For more information on how to join our Precision Bridge Partner Program, please click here.
New Hires
We’re excited to welcome Thomas Moore to the Precision Bridge team as our Junior Python Developer. Tom will be supporting our development efforts, helping to build and improve the tools that make complex data migrations faster, smarter, and more reliable. As demand for data migration solutions continues to grow, his role will be key in helping us scale our technology and deliver even more value to our clients. We're thrilled to have him on board!
Simplifying Data Management for Service Management Systems: Intelligent Automation
There is plenty to think about when setting up a Service Management system, and this does not stop when it is up and running. Even if you have used the latest data migration automation solution to make sure you have all your valuable data on your new system in exactly the right formats and exactly the right locations with all the references and links working, you still have ongoing data management activities to consider.
One area is data replication. Backup is one obvious use case for data replication but there are several others. Other common use cases for data replication are reporting and analytics. This can be required where there is a need to bring together data in a centralized location, such as a data warehouse, data lake or lake house, so that reporting across multiple applications can be achieved from one location. Additionally, many systems charge per user and there can be situations where data can be replicated to other systems for access for a subset of users, reducing the licensing requirement and costs.
Click here to read the full blog post.
Upcoming Webinars
We continue our popular webinar series with the following:
July 2nd at 11 AM EST: Live Demonstration: ServiceNow Instance Migration - Moving to Greenfield
July 16th at 11 AM EST: Live Demonstration: ServiceNow Data Archiving
July 23rd at 11 AM EST: Gen AI: How Does It Actually Work? Webinar
See our webinars page for more information and to register or visit On Demand Webinars for a list of all on-demand webinars.
If you would like more information about Data Migration, Archiving, Replication automation or Precision Bridge then contact us here.
Final Thoughts
We round off this Newsletter with one of our Service Management Migration Guide Hints and Tips. You can get a copy of the full guide by attending one of our Data Migration Webinars.
Tip 7: Preserving Data Integrity
Another key area is the relationships within ITSM applications as these are an important part of the application integrity so it’s important to preserve these wherever possible. There are numerous examples of relationships such as: Relationships in the current system can be difficult to transfer to the new one, especially if you are migrating to a different vendor platform. For example, reference fields in ServiceNow may use different sys-ids on current and target systems. And, when migrating from a different vendor platform, relationships may be stored in a separate join table which does not exist on the new one.
Simple extraction and re-importing of the ITSM records can compromise the integrity of relationships so these need to be examined and processed separately to ensure that integrity is maintained. In many cases, this can affect the ordering or data loads since relationships create dependencies between records. One-to-many relationships are also tricky to migrate - they might be stored as a list in a single field on the current system and as separate records on the new one. In these cases, additional work may be required to extract the required record identifiers so that they can be loaded in the correct format as separate records.
TIP 7: Review the relationships and verify that the migration approach and any tools you will be using will maintain the data relationships.