Linear is not a CRM, so you connect the CRM you already use: Salesforce connects natively on Linear Enterprise, HubSpot connects through IssueLinker, and without a CRM you can enter customers by hand. Each route fills Linear's Customers feature, a record per account with owner, tier, status, revenue, and size, linked to the issues that customer asked for. Find your CRM below.
| Your CRM | How it connects to Linear | Customer data in Linear | What it needs |
|---|---|---|---|
| None, or a spreadsheet | Customer requests added by hand or from Slack | Whatever you type in | Any Linear plan |
| Salesforce | Linear's native Salesforce integration | Owner, tier, status, revenue, size from the account | Linear Enterprise, plus the add-on |
| HubSpot | IssueLinker, from the HubSpot ticket | Owner, tier, status, revenue, size mapped from the HubSpot company | IssueLinker, $39 per month, any HubSpot plan |
| Attio, Pipedrive, others | Zapier, Make, or the CRM's own Linear app | Usually one way, field by field | Depends on the tool |
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
Is Linear a CRM?
No. Linear is an issue tracker built for product and engineering teams. A CRM keeps a record for every contact and company, logs emails and calls against it, tracks deals and revenue, and feeds marketing and support. Linear does none of that.
What Linear added in December 2024 is a narrower idea: let engineering see which customers are behind each piece of work. That is the job of Linear's Customers feature, and it is why people search for a "Linear CRM". They do not want to run sales in Linear. They want customer context next to the issues.
Teams searching for a Linear CRM rarely want Linear to become a CRM. They want the CRM's customer data to show up where engineering decides what to build next.
What Linear's Customers Feature Covers
Every Linear customer is an account with a name, its domains, and five attributes. Customer requests then link that customer to issues and projects, each request carrying the original message and a link back to where it came from.
Owner
The account owner, usually the CSM or account executive, matched to a Linear user.
Tier and status
Labels such as Enterprise or Startup, and Active, Trial, or Churned. Filter issues by the tier of the customers asking for them.
Revenue and size
Numbers you can order projects by, so the work behind the most revenue rises to the top.
The feature is only as good as the data in it. Typed in by hand, revenue and tier go stale within a quarter. Synced from a CRM, they stay current, and that is the whole case for connecting one. Our Linear customer requests guide covers how requests are created and how to prioritize with them.
Option 1: Use Linear Customers on Its Own
If you have a handful of customers and no CRM worth syncing, start inside Linear. Add a customer request to an issue from its Customers section or with the keyboard shortcut, or turn a Slack message into a request. Set each customer's tier and revenue by hand.
This works until it does not. The moment several people log requests, customer names drift, revenue goes out of date, and a churned account still looks like your biggest one. That is the signal to connect a CRM.
Option 2: Salesforce, Connected Natively
Linear's Salesforce integration is the only native CRM connection. It syncs account data into Linear customers and creates a customer request when someone links a Salesforce case to a Linear issue. In Settings, under Customer requests, you map each of Linear's five attributes to a Salesforce account property: owner to an email, tier and status to text fields, revenue and size to numbers. Linear then pulls updates automatically, so the records stay current.
The catch is the plan. The Salesforce integration is an add-on to Linear's Enterprise plan. For a large company already on Enterprise it is the obvious choice. For a startup on Basic or Business, it means a plan change before you sync anything.
Option 3: HubSpot, Connected Through IssueLinker
HubSpot is not one of Linear's native customer data sources, so a HubSpot ticket does not reach Linear on its own and neither does the HubSpot company behind it. For teams that run support on HubSpot Service Hub, IssueLinker closes both gaps from the ticket.
- 1
Create or link the Linear issue from the HubSpot ticket
A card on the ticket opens a new Linear issue or links an existing one in one click, with the ticket conversation carried over. AI can draft the issue from the full thread.
- 2
Attach the HubSpot company as a Linear customer request
With customer requests turned on, IssueLinker takes each HubSpot company associated with the ticket, creates or reuses the matching Linear customer, and attaches a customer request to the issue. The same HubSpot company always maps to the same Linear customer, so requests add up on one record instead of creating duplicates.
- 3
Map HubSpot company properties to Linear's customer fields
Choose which HubSpot company properties fill revenue, size, owner, status, and tier. The owner is matched to a Linear user by email, and the tier and status arrive as their labels, not HubSpot's internal values.
- 4
Keep the ticket and issue in step
Comments sync both ways in real time, and the Linear status is written back to the ticket, so support knows when the fix ships and the customer hears back.
IssueLinker costs $39 per month flat, never per seat, and works on any HubSpot plan, including free. Customer requests is a setting you turn on. The first time, it asks you to reconnect HubSpot and Linear once, to grant read access to HubSpot companies and write access to Linear customers.
Put HubSpot customer data next to your Linear issues
IssueLinker turns a HubSpot ticket into a linked Linear issue in one click, attaches the HubSpot company as a Linear customer request with revenue and tier, and syncs comments and status both ways. $39 per month, any HubSpot plan.
Option 4: Other CRMs
Attio lists Linear among its integrations, and newer CRMs often ship their own Linear app, so check your CRM's marketplace first. For anything else, Zapier and Make can create a Linear issue or customer request when a CRM record changes. Those flows usually run one way and field by field, so treat them as a starting point rather than a sync: nothing keeps the Linear customer current after the first write unless you build a second flow for it.
Which Linear CRM Setup Should You Choose?
Free on any plan. Log requests by hand and from Slack, and connect a CRM once revenue-based prioritization matters.
The deepest native sync, with account data pulled automatically. Not worth a plan upgrade on its own.
Tickets become Linear issues with the HubSpot company attached as a customer request, mapped to revenue and tier, on the HubSpot plan you already have.
What a Linear CRM Connection Should Do
Whichever route you pick, test it against the job it is there for: putting accurate customer context next to engineering work.
Before you commit
- One account in the CRM maps to one customer in Linear, not a new duplicate per issue.
- Revenue and tier in Linear match the CRM, and change when the CRM changes.
- A request created from support carries the original message and a link back to the ticket.
- The person who reported the problem hears back when the issue ships, without someone checking Linear by hand.
- The setup works on the Linear and CRM plans you already pay for.
If you are also weighing trackers, our Jira CRM guide covers the same question for Jira, and the Linear HubSpot integration guide walks through every way to connect the two.
