Legacy Data Migration - what to send to ITpipes?

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:

  1. A single database that houses all assets and inspections to be converted; if additional data is sent after the initial submittal there may be additional costs.
    1. If the data is in a compliance standard such as SPICAP, NASSCO MACP, PACP, LACP, SCREAM or similar, please export the data into the exchange database format.
  2. If media conversion is part of the quote, all media such as video and picture files that are referenced in the database to be converted. Note: if there is extra media that does not match the database, this media will not be converted; ideally sending only the media that matches the database will streamline the process of transferring data to ITpipes.
  3. If an excel sheet listing all assets is available, that may be valuable to compare in case multiple inspections exist for a single asset and those assets will need combined.
How to get data to ITpipes.
  1. This KBA provides information on how to get data to ITpipes.

Note: Once the data has been received, we will need to confirm and have approval from a client representative on the ITpipes template that is going to be used.  The ITpipes template, once approved, can not be modified until the legacy data migration is complete. If the template is changed during the data migration, the migration will need to start over from scratch with the new template. Once the data arrives at ITpipes, if the template was not approved within the last 60 days, we will reach out to the client representative obtain this or review our last version to have this approved. 


Note 2: Often inspections are created after legacy data is sent to ITpipes for migration. In that situation, an interim data set may need sent to ITpipes after the upgrade is complete. If that is the case, please be sure to note the date you originally send data to ITpipes. Then next time data is sent please only includes “new” data collected since the original send date, this will save you and us time. See here for more details.


Any questions, please feel free to email us at techsupport@itpipes.com. We look forward to checking out your inspections!  


    • Related Articles

    • 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 ...

    • 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 ...

    • How to send ITpipes data via ShareFile and FileZilla FTP

      Sharefile Account You will need an ITpipes provided sharefile account in order to send data to ITpipes.  Please fill out this form to request one. Download FileZilla If you do not already have FileZilla FTP Client, you can find the download link ...

    • 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 ...

    • ITpipes and ESRI Documentation

      Table of Contents Introduction ITpipes integration with an ESRI geographic information system (GIS) is a powerful way to leverage the capabilities of these advanced systems. This document covers various components of this integration. The purpose of ...