Get your customer data into the CRM in the layout it imports.
The three CRM packs ship layouts for each CRM's own import tool, neutral source layouts and mappings between them. They read and write files and do not call the CRM's API.
A CRM import fails on one misnamed column or a parent record that does not exist yet. Getting accounts, contacts and deals into the right shape, in the right order, is the real work.
Modules. Any paid module opens the Marketplace. Add Transfer to deliver files and Flow to schedule.
Edition. DataBridge Server or Desktop for the file work.
How DataBridge does it.
Each step names the feature as it appears in the product.
- Step 1
Neutral source layout
Describe your data once: Customer Contact, Sales Opportunity or Product Catalog, plus Support Case for Salesforce and Dynamics.
- Step 2
Field mapping
The pack's mapping turns that layout into the CRM's import layout.
- Step 3
Validate File
Check the output against the CRM template and list every problem before the import runs.
- Step 4
Relationships
Child files point at parents with the CRM's own relationship columns, such as Account.External_ID__c for Salesforce. Each pack's guide gives the load order.
- Step 5
Deliver
Write the files to a folder or push them to an SFTP server, then load them with Data Loader, HubSpot's import tool or the Dynamics 365 Import Wizard.
What this does not do.
- These packs do not call the CRM's API. A person or script still runs the CRM's import.
- The Salesforce account mapping is skipped unless the QuickBooks pack, or your own Generic Customer template, is installed. Check What's included after you install.
Marketplace packs used: Salesforce CRM Pack, HubSpot CRM Pack, Dynamics 365 CRM Pack. See the Marketplace.
Related pages.
Try the parts that are free today.
The free browser edition needs no sign-in and never uploads your files.