This guide will cover the process of importing a DealerTrack general ledger into MindBridge.
The recommendations provided in this article are based on data we have gathered at MindBridge that looks at the most common column mappings provided by our users for DealerTrack.
It is recommended to always validate the mappings before you complete them, and if in doubt check with your client or business owner. Reach out to the MindBridge Support team for additional assistance.
- Import your general ledger file into MindBridge through the File Manager, or by importing directly to the General Ledger section on the Data page. For step-by-step instructions, follow our Import a general ledger guide until the Map Columns step.
- At the Map Columns step, we recommend to map the DealerTrack fields as follows:
|MindBridge Column||DealerTrack Column Name||Possible Alt Column Mappings||Fields used in MindBridge||Used in Analytics*|
|Account Description||[Not commonly mapped]||Optional||No|
|Type||[Not commonly mapped]||Optional||Yes|
|User ID||[Not commonly mapped]||Optional||No|
|Entered Date||[Not commonly mapped]||Optional||Yes|
* Optional columns, even if not used in the analytics, can be included for filtering and other visualizations.
** Transaction ID is required but does not necessarily need to be in one single column. In the Review Data step of the ingestion process, MindBridge will recommend a transaction ID based on your data, or you can choose and/or combine different columns to create one. For more information: Understand Transaction ID and data integrity
What do you think of this guide? If you have any feedback, or you think you can help us improve it, then we would love to hear from you! Please contact us at email@example.com. We are offering rewards for any information that leads to the improvement of a guide or the creation of a new one.