Salesforce-Microsoft Dynamics NAV Integration
Direct integration between Salesforce and Microsoft Dynamics NAV, so sales and finance work from the same customers, orders and invoices. Configured on screen, not written in code, and supported by the people who built it.
Automate the order to cash process
Connect Salesforce with Microsoft Dynamics NAV to move orders, keep customer accounts aligned, and send finance data back to the CRM. Accounts, contacts, products, prices, orders, invoices, credit notes and ledger entries are in the standard template, across one NAV company or several.
Send orders to Dynamics NAV
At a trigger point you choose, for example when the first quote is accepted, Rapidi creates the customer, the contact and the order in NAV. The NAV sales order number is written back to the Salesforce opportunity.
Keep customer accounts in step
Accounts and contacts sync in the direction your process needs, one way or both, so sales and finance stop arguing about who updates which system.
Return invoice and payment status
When an order is invoiced in NAV, it leaves the open orders in both systems and comes back to Salesforce as a posted invoice. Payments follow as ledger entries, so the account shows balance and payment history.
What you can integrate
These objects are mapped in the standard template. Any table can be integrated in any direction.
Salesforce
Direction
Dynamics NAV
Accounts
Customers
Contacts
Contacts
Products
Products
Prices
Prices
Opportunities
Orders
Orders
Orders
Payments
Ledger entries
Sales history
Invoices and credit notes
Any object, standard or custom
Any object, standard or custom
Get the template
You start from the template built for this pair rather than a blank canvas. There are two versions, one for NAV 2009 and earlier and one for NAV 2013 and later, so tell us which one you run. Point Rapidi at your Salesforce org and your NAV database, then map the fields your business actually uses on screen. The template handles several NAV companies and currencies from the start, and you switch off the parts you do not need.
Integration features
Built for one pair of systems rather than assembled from a toolkit, and specified so a technical buyer can qualify it before the first call.
Pre-built pair template
A template built for Salesforce and Dynamics NAV specifically, not a generic connector you assemble yourself. Customers, contacts, products, prices, orders, invoices, credit notes and ledger entries are mapped before you start.
Per-object timing
A schedule you set, chosen object by object: daily, hourly, every 10 minutes, every minute or triggered, depending on your subscription. A schedule runs a group of transfers in the order you define, and you can create as many schedules and transfers as you need.
Fast reads, validated writes
Where NAV runs on SQL Server, Rapidi reads straight from the database, which is fast and picks up only changed records by timestamp. It writes through NAV Web Services, so new data passes through NAV's own code and validation. Both connectors are included in the subscription, and older versions are reached through C/Front.
Failed transfer reporting
When a transfer fails, for example on invalid source data or a dropped internet connection, Rapidi logs the error and emails you the message with a direct link to it. You set the rules for how and when you are told.
Reaches systems inside your network
The RapidiConnector sits inside your network next to NAV and opens one outbound port. If your NAV Web Services are hosted online by Microsoft or a partner and exposed to the internet, Rapidi can connect to them directly instead.
Access on your terms
On SQL, Rapidi connects as a normal SQL client, with access permissions handled at normal user level on your server, and takes up one session while transfers run. On Web Services it signs in with the Windows user you set up.
Built around your NAV version and companies
Dynamics NAV runs in many versions and often in several companies at once, and the standard integration is set up for both.
- There are two versions of the standard integration, one for NAV 2009 and earlier and one for NAV 2013 and later. You tell us which one applies when you order.
- The standard solution supports several NAV companies and several currencies from the start. If you run one company, that part is removed.
- A Legal Entity picklist on the Salesforce account decides which NAV company a customer belongs to, and contacts and opportunities inherit it. It is only needed if you have more than one company.
- NAV changes are kept small. A few fields are added to some tables, for example an ExternalID on Customer and Contact to hold the Salesforce ID, using field numbers from 50,000 upwards.
- For NAV 2009 and older, the C/Front module (module 1800) must be included in your NAV licence so Rapidi can reach the data.
The eight most common integrations
The transfers most Salesforce and Dynamics NAV customers start with, and why each one earns its place.
1. Account to Customer
An order has to be linked to a customer before it can be processed, and the account usually starts life as a lead in Salesforce. The usual direction is Salesforce to NAV, and it can run both ways so sales and finance both maintain the record.
2. Contact to Contact
In most NAV setups a main finance contact is all that is needed, so this transfer is often limited. Contacts are master data and the hardest to keep clean, because people change role, employer and name. Never transfer data you do not implicitly trust.
3. Product to Item
If quotes are built in Salesforce, product data has to be there. Products and Items are the same thing under different names, so the mapping needs someone who knows both systems. It runs one way or both, depending on where new items are created.
4. Item price to product price
The two systems price and discount differently. NAV pricing and discount models are converted into Salesforce price books, often including the currency dimension. Once the method is in place it is reusable.
5. Quote to Order
The quote becomes a sales order in NAV automatically, instead of totals being keyed by hand and Salesforce updated afterwards. Sales then works only in Salesforce, so you do not buy sales user licences for both systems.
6. Sales order to sales order
The order syncs back so the account and opportunity show the full picture, and keeps syncing through order changes, part delivery, part invoicing and product substitutions.
7. Sales history
Booked invoices move from NAV to Salesforce, with credit memos for the full picture. An invoice has a header and lines, so this is several tables. Sales history is what the Salesforce AI features use for predictive work.
8. Payments
Ledger entries complete the quote to cash loop and surface payment patterns and overdue amounts on the account. Useful to sales, useful to cash collection, and useful as a negotiation parameter.
Quick facts about the solution
| Feature | Description |
|---|---|
| Data transfer | Data is SSL encrypted, packed and compressed by the RapidiConnector. |
| Salesforce API and access | Rapidi is Salesforce certified, which lets you integrate Salesforce Pro Suite without buying Salesforce API access. |
| UPSERT | Rapidi can use UPSERT when writing to Salesforce, processing 200 records in one API call instead of one call per record. |
| Dynamics NAV API and access | Web Services for write, SQL Client for read. For NAV 2009 or older, C/Front (module 1800) is required. |
| Security | Encryption follows the current TLS standards, TLS 1.2 and TLS 1.3 preferred. |
| IP address and firewall | No fixed IP addresses, and no inbound ports opened on your firewall. |
| RapidiConnector | Connects Dynamics NAV with your Rapidi service, then compresses, packs and SSL encrypts the data. |
| Read design | One click reads the database design, so every table and field is available for mapping. |
| Data mapping | Any table or field can be synchronised. Field lists, filters, sub transfers such as sales header and lines in one transaction, and tags to reuse a mapping. |
| StoreNewID | Writes the key one system assigns back to the record in the other. A new NAV Customer No. is written to the Salesforce account in the same transaction. |
| New or modified data only | Changes only where tables carry timestamps, and Mirror where they do not, so only new and changed data moves. |
| Transfer frequency | Daily, hourly, 10 minutes, 1 minute, or triggered, depending on subscription level. |
| Advanced data toolbox | Excel-syntax formulas to align formats and field structures. Ready-made formulas ship in the standard templates. |
| Log and notification | Rapidi records detailed information about every schedule and transfer, and no customer data. |
| AI agent | Albert, the Rapidi AI agent, assists with your integration setup and can perform tasks on it. |
Get the fact sheet
The Salesforce and Microsoft Dynamics NAV integration on 6 pages: the key benefits, the object map with directions, the supported versions and the technical quick facts.
One short form, the PDF on the next page.
Security and deployment
Your systems are never exposed to the outside world.
- On-premise Dynamics NAV goes through the RapidiConnector, which sits inside your network and compresses, packs and encrypts data before it leaves. NAV Web Services hosted online and exposed to the internet can be reached directly.
- Encryption follows the current TLS standards, TLS 1.2 and TLS 1.3 preferred. You can use your own SSL certificate.
- One outbound port. No fixed IP addresses, and no inbound ports opened on your firewall.
- Data is processed end point to end point in memory. No customer data is stored on any Rapidi server, and configuration data is stored encrypted.
- Rapidi monitors your setup and contacts you when a server stops responding or invalid data is being exchanged.
- The connector protocol strips metadata and sends compressed binary, cutting data volume by up to a factor of 50: roughly 20 bytes per customer record instead of 1000.
What our customers say about Rapidi
What we support
Salesforce editions
Starter Suite, Pro Suite with API access included, Enterprise, Unlimited and Einstein 1. Rapidi is Salesforce certified and Lightning ready.
Dynamics NAV versions
NAV 2018, 2017, 2016, 2015, 2014 and 2013, NAV 2009, and NAV 5, 4, 3.70 and 3.56. For NAV 2009 and older, the C/Front module (module 1800) must be in your licence. Newer versions are covered by the Salesforce and Business Central integration.
Dynamics NAV databases
Microsoft SQL and the Microsoft Dynamics NAV native database.
Dynamics NAV data inside Salesforce
The Rapidi Sales History App puts posted invoices, customer ledger entries and, with an add-on, open sales orders from Dynamics NAV on the Salesforce account. Sales people drill down into orders and history, look up accurate pricing and see the main sales KPIs without leaving the CRM.
The app is unmanaged, so you can customise it, and the history can be linked to other objects such as the opportunity. Roll-up summary fields calculate totals like sales this financial year without running a report.
Rated by the people who run it
Scores from the review sites your own procurement team will check.
4.95
Salesforce AppExchange
out of 5, from 62 reviews
4.8
G2
out of 5, from 5 reviews
5.0
Capterra
out of 5, from 5 reviews
Customer success stories
See what our customers have to say
Companies running Salesforce alongside Microsoft Dynamics NAV. Each card opens the full case story.
Integration specialists since 1987
Rapidi is data integration and replication software for Microsoft Dynamics, Salesforce and HubSpot. Microsoft partner since 1987 and Salesforce partner since 2007, with 56 documented connectors and integration and replication in the same product. The company builds the templates, runs the support, and answers the phone.
Frequently asked questions
Ready to connect Salesforce and Dynamics NAV?
Tell us your Salesforce edition, your NAV version and how many NAV companies you run, and we will tell you plainly what the template covers and what it costs.