Legacy Data Migration - Interim Data during Services Project or Implementation

Legacy Data Migration - Interim Data during Services Project or Implementation

During an implementation or services project, often interim data needs followed up on. This is data collected or obtained between the time of the data being sent to ITpipes and the data going back to the client and/or the new system being used. There are two potential scenarios outlined below.

Interim data created while upgrading from ITpipes Desktop to ITpipes Mobile or Web

We understand inspections will still be happening during the migration and upgrade process.  Based on that, we have two options for migrating the interim inspections.  
  1. ITpipes can help you export a dataset and media from ITpipes, using the cut off dates you provide, so the new data can be sent to ITpipes using the form and/or method previously used to send the initial data set for migration.
  2. ITpipes can set up Sync in the cctv units to continuously sync new data into ITpipes Web, this may require a video conversion process depending on the Desktop setup.  This will simply keep syncing inspections during the upgrade process.

Interim data created from 3rd Party App while upgrading to ITpipes

We understand inspections will still be happening during the migration and upgrade process using the 3rd party field software..
Based on that, when the move from the 3rd party application to ITpipes is made, ITpipes requests that you export a dataset and media from the 3rd party application, using the cut off dates based on previous data sent.  If a compliance standard such as PACP was used to collect the data, a PACP export is required to migrate this data and media. The new data can then be sent to ITpipes using the form and/or method previously used to send the initial data set for migration.

Please keep in mind if all legacy data is resent, this will take ITpipes time to sort through and longer for you to upload, using the cutoff date to only move “new/interim” data, will save many hours of effort moving data.

Interim data can be sent to ITpipes different ways, as outlined here.

    • Related Articles

    • Legacy Data Migration - what to send to ITpipes?

      Prior to starting an implementation, that includes legacy data migration, the legacy data needs provided to ITpipes and a form needs completed. The data sent to us for migration should include the following: A single database that houses all assets ...
    • Data Migration Review Recommendations

      No one knows your data like you. This article provides recommendations on data QA/QC checks for reviewing data converted into ITpipes. ITpipes SmartTabs will be invaluable for doing QA/QC on data and we recommend attending ITpipes Web Usage training ...
    • ITpipes Implementation Timeline for Mobile, Sync, Web and Cloud

      This is a general timeline for an ITpipes implementation with products including Mobile, Sync, Web and Cloud*. Please keep in mind this timeline does vary based on all requirements being met, based on client resources and responsiveness, legacy data ...
    • Prep to complete Data Migration Form

      When a data migration is performed, it is critical we know what you expect to be migrated, therefore we require this form be completed.  During the sales process, the ITpipes representative will have provided an estimate based on discussions and a ...
    • Video Conversion - Converting videos from other formats into an ITpipes Web format

      Video Conversion ​If you are converting a large amount of media, ITpipes has built an in-house a multi-processor usage application that quickly converts video. We run these simultaneously on several powerful systems and its rare that any project has ...