Turvo Data Importer (TDI): Customer Data Request

Start your Turvo data migration by collecting and providing Turvo with the master and historical data you wish to migrate from your previous system of record. Keep in mind that your Turvo contract and timeline may impact which entities will be uploaded.

Note: Shipment and order data is limited to up to 12 months of historical data.

Organizing your data into Turvo Entities

Follow these two steps to execute the TDI process in the fastest way possible to import your data. 

  1. Categorize your data to correspond with Turvo’s Entity structure listed in the table below without manipulating your extracted data.
  2. Prioritize master data before transactional data. See the table key for identifying master and transactional data. Orders and shipments are considered transactional data, all others are master data.

Turvo’s Entities

1. Group†

8. Location†

2. User†

9. Contact†: If associated with other entities, highlight contact info in associated data.

3. Parent†

10. Asset†

4. Factor†

11. Items†

5. Carrier†

12. Order‡

6. Customer†

13. Shipment‡

7. Other account†

14. Routing Guide†

† = Master data     ‡ = Transactional data

Data Review

Here are some guidelines for reviewing your data:

  • Some of the Turvo entities have specific use cases that may require additional discussion with your onboarding manager. As an example, you may not utilize Groups today, however, you may want to apply these within Turvo.
  • Designate at least one primary point of contact that Turvo can connect with to discuss data use cases and clarifications.

File Types

Turvo only accepts CSV file types. If this is an issue, contact the Turvo data team.

Data collection considerations:

  • Avoid duplicate entities: Do NOT manually create entities in Turvo you wish to migrate. This includes Users. Doing so will create duplicates or issues during the migration.
  • Collecting master data: Turvo prefers one complete data sheet for the following master data entities; Users, Groups, Contacts, Factors, Locations, Carriers & Customers.
  • Providing master data: Ensure the data you provide is up-to-date with when your Turvo onboarding begins.
  • Providing gap data: There may be a gap between when data is provided and when you go live. To account for this gap please provide gap data on your go-live date.
  • Dummy carrier DOT or MC values may NOT be used unless approved by Turvo.
  • Carrier DOT or MC numbers: We currently do NOT support different carriers who operate under the same DOT or MC number.
  • Multiple files for a Turvo entity: Group multiple files for a Turvo entity into a single folder.
  • Data review: You can review both the UI and files used for upload in your sandbox environment prior to uploading your data into production.
  • Data points may not be convertible: Data points from your historical system in Turvo may not be able to be converted. We will do our best to map these data points to similar or alternative fields.
  • Complex data associations: Please provide clarification for  any data points that do not have a clear purpose or have complex associations with other data points.
  • Data questions and clarifications: Once customer data is received and reviewed by the data team, Turvo may compile questions that we will need to ensure accurate upload.
  • MCP or RMIS integrations: The majority of the MCP or RMIS carrier data will be synced from the third party, and may be best to upload minimal carrier details such as MC/DOT and SCAC.

Cleaning Your Data

Turvo requires that you clean and normalize your data before sending it to Turvo. Turvo reserves the right to reject any bad data and requires that your data is clean before Turvo moves forward with the migration process. This can lead to delays in the migration/onboarding timeline. Clean and normalize data by:

  • Removing or standardizing any duplicates
  • Ensuring there are 1-to-1 mappings, where applicable
  • Confirming that your Master Data matches with ALL reference points in the historical data you provide
  • For numerous reasons, data can often be located in fields they are not meant to be in. Do your best to identify and relocate this data. Turvo is NOT responsible for the misrepresentation of this data in the UI
  • Consider that Turvo may not support the data you want to migrate

** Note: If you have any questions, concerns, or doubts about the above guidelines required to clean your data, please contact the Turvo Representative assigned to your data migration project.

**For more in-depth information about TDI, see the Introduction to TDI article.

Was this article helpful?

0 out of 0 found this helpful