A services organization we're moving off Salesforce asked us a practical question recently: their team generates quotes today, some automatically and some by hand, and they wanted to know how that same work happens in Dynamics 365. The mechanics are different, but the pieces map over reasonably well once you know the names.
Where the price comes from
In Salesforce, products live in price books, and a quote pulls from whichever price book applies to that department or service. Dynamics 365 uses the same idea under a different name: a price list. You attach a price list to an opportunity, and when you add products, the system shows only the items on that price list with their prices. So the concept carries over. The clicks are just in a different order.
One thing worth sorting out early: how each price is set. In this client's case, some items had a preset price and others were entered per quote. That distinction matters when you set up product records, because a fixed-price item and a manually priced item get handled differently.
Line items versus attached documents
There's a real fork in how you build a quote, and it's worth deciding on purpose:
| Approach | When it fits |
|---|---|
| Attach a finished document to the record | The quote is generated elsewhere (for example by a submission or intake tool) and you just need a copy on file |
| Build the quote line by line in the system | You want the products, quantities, and totals stored as data you can report on and reuse |
This client had both patterns. Some quotes were auto-generated by outside software and simply landed as files on the record. Others were built line by line inside the record, product by product, off the right price list. Knowing which quotes need to be real data versus just a stored PDF shapes how you configure the system, so it's a question worth answering before the build, not during it.
Turning a quote into a polished document
Once the quote data lives in Dynamics 365, you still want it to come out looking like your quote, not a raw data dump. Dynamics 365 supports Word-based document templates for this. You design the layout in a Word document, then map each spot in the document to the field it should pull from (this line maps to the quote table, that field maps to the rate, and so on).
You can store more than one template per table. If you need a different quote layout for different departments or purposes, you keep several templates with clear names, and the logic picks the right one for the situation. Depending on how you set up the process, the system can fill the template and, if you want, send it out automatically once the intake form is processed.
Decide up front whether a generated quote goes out on its own or waits for a person to review it. Both are possible; it's a workflow choice, and the answer can differ by quote type.
Thinking through your quoting flow
The short version: Salesforce price books become Dynamics 365 price lists, product-by-product quotes are supported, and a Word template plus field mapping gets you a clean document at the end. The details depend on how many quote types you run and how much you want automated. If you're mapping out a move and want to talk through how your quoting should work in Dynamics 365, we're glad to help.