Importing the data into your CRM

Our customers mostly use the files to enrich account records rather than to create new ones from scratch. The routine below works in Salesforce, HubSpot, Dynamics, and most other CRMs.

One-time setup

1. Add custom fields to the Account (or Company) object for the attributes you care about: Dealer Group, Website Provider, Digital Retailer, Makes, and AMD Last Updated.
2. Pick a match key. Website domain is the most reliable. Normalize both sides: lower case, strip http(s)://, www., and trailing slashes.
3. Decide on create vs. update. Most teams update existing accounts and route unmatched rows to a review list rather than auto-creating thousands of accounts.

Each month

1. Download the new file from the link in your delivery email.
2. If you are loading the Dealer Tech Vendor data file, pivot it first so each dealer is one row with a column per vendor type (website, digital retail, chat, …). A spreadsheet pivot table or a short script handles this.
3. Run your CRM’s import tool in update mode, matching on the normalized domain field.
4. Set AMD Last Updated to the file date so reps can see freshness.
5. Review the unmatched list; these are often new rooftops, renamed stores, or dealers that changed domains.

Useful automations once the basics work

• A report of accounts whose Digital Retailer or Website Provider changed since last month — a strong trigger for outreach.
• A report of accounts whose Dealer Group changed — the store was bought or sold.
• Lead routing by Dealer Group, so group-level accounts reach the right rep.

If you would like help designing the import for your specific CRM, email info@automotivemarketdata.com.