Most DJs don’t have a contact database. They have an Instagram inbox and a hope that the conversations they need will resurface when they need them. This works until it doesn’t, and the moment it stops working — usually somewhere around the 200-thread mark — the cost is hidden but real: missed bookings, dropped collaborations, dead leads that should have been reactivated.
Building a proper contact database isn’t complicated. It is, however, something most artists never get around to because the setup feels heavier than the immediate payoff. This guide is a working blueprint: what to include, where to host it, how to populate it from your existing Instagram history, and how to maintain it without it becoming another item on your to-do list.
Why “database” instead of “list”
A list of contacts is what’s in your phone. A database is what’s in a CRM.
The difference matters. A list lets you find someone by name. A database lets you ask questions: who haven’t I talked to in three months? Which promoters in Berlin have I met? Who owes me a reply, and on what topic?
Those questions are the entire reason the database exists. If you can’t filter, sort, and view your contacts in different ways, you have a list — and lists at scale are no better than a buried inbox.
The minimum useful database for a working DJ has the following capabilities:
- Filter by relationship status (cold, warm, active, in-negotiation)
- Sort by last contact date
- Group by city or scene
- Search any field (name, role, topic)
- Tag by event type (festivals, clubs, podcasts, labels)
Spreadsheets can do some of this badly. Notion can do all of it well. Airtable can do all of it powerfully. Pick your tool based on how much complexity you actually need.
What goes in the database
Per contact, the fields that earn their place:
- Name and handle. The basic identifier. Display name plus @username plus real name if you know it.
- Role. Promoter, label A&R, fellow DJ, agent, journalist, photographer, manager, venue staff. Sometimes someone wears multiple hats — note both.
- Affiliation. What venue, festival, label, or agency are they connected to? This is what makes the database actually queryable.
- City. Critical for tour planning and scene mapping.
- Source. How did you meet them? At a festival, through a mutual friend, cold DM. This is more useful than people expect — it tells you the texture of the relationship.
- First contact date. Helps you see how relationships develop over time.
- Last contact date. The single most useful field for staying on top of the network.
- Status. Where the relationship currently sits. Cold (no real activity), warm (open but quiet), active (current conversation), in-negotiation (specific deal in motion), closed (signed or done), dormant (was warm, now quiet >6 months).
- Last topic. What was the most recent conversation about?
- Next action. What specifically is owed, by whom, by when?
- Notes. The free-form column. Where you put the context that wouldn’t fit anywhere else: their style, their preferences, their network, anything you’d want to know if you re-engaged in six months.
Eleven fields. Some get populated automatically when you import; others you fill in over time. The database becomes useful when about half of these fields are populated for most contacts. It becomes powerful when nearly all of them are.
Where to host it
Three reasonable options:
Notion. The most common choice for working artists. Pros: flexible database views, easy to share with collaborators, large template ecosystem. Cons: search can be slow at scale, mobile experience is weaker than desktop.
Airtable. More powerful relational structure. Pros: real database engine, excellent filtering, automation features. Cons: pricing scales fast if you have many records, more learning curve.
Spreadsheets. Google Sheets or Excel. Pros: zero learning curve, free at most usage levels. Cons: weak views, no real CRM affordances, painful at scale.
For most DJs starting from scratch, Notion is the right answer. It’s flexible enough to grow with you, mobile enough to update on the road, and shareable if you eventually bring on a manager or assistant. If you’re already a heavy spreadsheet user and want to stay that way, that’s fine — but expect to outgrow it around the 300-contact mark.
How to populate it from your Instagram
This is where most setups die. You build the structure, you stare at the empty database, and you don’t know how to fill it without manually copying hundreds of conversations from Instagram.
There are three paths:
Manual entry. Open Instagram, open your database, copy across one contact at a time. This works for small networks (under 50 contacts) and absolutely doesn’t work at scale. The temptation is to do “the most important ten” and call it a day, but the ones you forget to enter are usually the ones you’d benefit from re-engaging.
Hybrid: export, manual triage. Request your Instagram data export, open the JSON files, and use them as a reference while manually populating the database. Faster than pure manual because you have all the data in front of you, slower than automated because you’re still doing the data entry yourself. Reasonable middle ground for someone with technical comfort.
Full automation. Tools that take your Instagram export and produce a populated database directly. Backline is built specifically for this — it parses the export over an encrypted connection and outputs a Notion CRM with the basic fields filled in: name, handle, last contact date, last topic, message count, status (cold/warm/active inferred from activity patterns). The free tier handles smaller exports; paid tiers handle larger archives.
The choice depends on the volume. Under 50 contacts, manual is fine. 50–200 contacts, hybrid is the sweet spot for technical users. 200+ contacts, automation is the only realistic option unless you enjoy data entry as a hobby.
The fields you fill in over time
Some database fields can’t be auto-populated. They require human judgment.
Status. A tool can guess based on activity patterns, but only you know whether a quiet conversation is “warm but waiting” or “actually dead.”
Notes. The free-form context. The thing that makes the database useful three months from now when you’ve forgotten everything.
Affiliation and role. Sometimes the conversation makes it obvious. Often it doesn’t. You’ll need to fill these in manually as you triage.
Next action. This one is critical. Without a “next action” field, the database becomes a passive archive. With it, the database becomes a to-do list you can prioritize.
The discipline is filling these in as you go. Every time you have a real exchange with someone, the next action gets updated. Every time something resolves, the status changes. Every time you learn a new piece of context, the notes get richer.
This is, in fact, what 90% of CRM work is: not the initial setup, but the ongoing maintenance of these soft fields. Tools can do the import. Only you can do the curation.
The maintenance ritual
A populated database that doesn’t get maintained becomes stale within three months and useless within six. The maintenance ritual that keeps it alive is roughly an hour a week, broken into two passes.
Monday morning, thirty minutes. Open the database. Sort by next action. Execute or schedule everything for the week. Sort by last contact date. For anyone in active or warm status who hasn’t been touched in three weeks, decide whether to follow up or de-prioritize.
Friday afternoon, thirty minutes. Capture the week. New contacts go in. Status changes get updated. Notes get filled in for any conversation that yielded interesting context. Two or three long-tail contacts get a re-engagement message.
That’s it. Sixty minutes a week to stay on top of a network that would otherwise drift out of focus.
When the database starts paying back
The first real win usually comes within the first month, when the orphan list — contacts that the database surfaces as “warm but quiet for more than 90 days” — produces its first reactivation. Someone you’d forgotten replies, a thread reopens, a small opportunity becomes real.
The compounding wins come later. After six months of consistent maintenance, the database becomes the place you go to plan tours, plan releases, plan outreach. You no longer guess at which promoters to contact for a Berlin date — you filter by city and status. You no longer wonder whether you’ve been in touch with a label recently — you check the last contact date. The database stops being a project and starts being infrastructure.
The bottom line
A contact database is the difference between running your career and reacting to your career. The difference compounds. By year three, the artists with databases are several rotations ahead of the ones still relying on Instagram’s interface to remember things for them.
The setup is a few hours. The ongoing cost is an hour a week. The payoff is everything that doesn’t fall through the cracks.
The data is already in your DMs. It just needs a place to live.
Backline produces a structured Notion CRM from your Instagram DM export — pre-populated with the fields above, ready for the maintenance ritual to keep it alive. Privacy-first: the file is processed over an encrypted connection — only message text is read, never sold, shared, or used to train anything, and visible only to you (a browser-only mode is available if you want zero upload). See how it works at backline.so.