I need to know the best method for writing customer data from our CRM directly into our service management space.
Hi Joel,
There are a myriad of connector apps out there that can help you with it. Personally, I would suggest starting with Peek Logic and Zappier. Others are just as good though. Get some demos and compare costs.
Hi @Fabian Lim
The product plan tag shows Standard.
As you solution is certainly an option, but on a standard plan the assets feature is not available.
So in this case @Joel Lehr needs to find a relevant 3rd party app, as mentioned by @John Funk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have details on the CRM?
I would also suggest the option to add the customer information into an Object Schema so that the information can be used outside of just the Jira Service Management space (Project). There are various plugins available depending on the CRM platform you use today.
Regards,
Fabian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If your goal is to bring CRM customer data into Jira Service Management as usable customer records, you can look at Mria Contacts: Contact Management in Jira & JSM by Mria Labs.
It’s built specifically for keeping customer data inside Jira and using it directly in support workflows.
With Mria Contacts, you can:
Import your CRM dataset via one CSV file that can create Contacts and Companies and link them during import (so you don’t end up with separate, unconnected lists).
Store customer attributes (job title, region, industry, etc.) and internal notes on the customer record.
Link JSM requests, Jira issues and Confluence pages/spaces to a Contact/Company
In daily JSM work, it helps like this:
When a new request is created, the app can match the requester email to an existing Contacts and Companies and suggest that match in the issue panel.
Once the agent links it, the ticket is connected to the customer record, and the agent can open the full customer view for history, details, notes, and linked documentation.
So instead of CRM data living only on tickets, it becomes reusable customer context inside Jira.
If you want to evaluate it, here’s the app:
https://marketplace.atlassian.com/apps/2263474600/mria-contacts-contact-management-in-jira-jsm?hosting=cloud&tab=overview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Joel Lehr,
Adding to the suggestions above, if you're on a Standard plan and want to avoid the complexity of external connectors, you might consider a more "native" approach.
Our team at Teamlead developed CRM for Jira specifically to help manage customer data without leaving the platform. It allows you to:
Centralize Customer Context: You can import your CRM dataset via CSV and have all company/contact details visible right inside the Jira issue panel.
Streamline Communication: A great way to keep everything in one place is to chat with customers directly from the Jira issue. This doesn't require extra JSM licenses for external users, which keeps costs down.
Automatic Matching: The app automatically identifies the reporter and displays the linked customer profile (contact and company) directly in the issue panel, providing instant context.
It’s a solid option if you want to turn Jira into a workspace where both data and communication live together. You can check it out on the Marketplace here.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.