How to choose art gallery management software

Choosing gallery software can look like a feature comparison, then turn into a more consequential question: which parts of the gallery’s working memory will be easy to carry forward, and which will become a separate file, an inbox search or somebody’s recollection?

That distinction matters because a gallery rarely handles a work in isolation. A work has an artist, a location, a status, a price, a condition, a history of conversations and a sequence of shows or fairs attached to it. A collector may be a buyer, an advisor, a lender and a guest at the same time. The right system keeps those facts legible when the person who entered them is not in the room.

Begin with the records that cannot be split apart

Most platforms can store a title, image and dimension. The more useful test is whether the record holds the context around the work without requiring a parallel notebook. A strong artwork record makes it clear what the work is, where it is, who is involved, what has happened to it and what can happen next.

When reviewing a system, open a sample work and follow its links. Can you move from the work to its artist, consignor, exhibition history, proposal history, documents and present status? Can you see the difference between available, reserved, on loan and sold? Can the team understand a past decision from the record itself?

Specialist products naturally place inventory, contacts, consignment and sales in the same working environment. Artlogic’s gallery-management overview describes those connected operational areas, while Artwork Archive’s gallery offering foregrounds inventory, client relationships and proposals. The point is not to collect every module. It is to decide which relationships your gallery needs to keep intact.

Use one sample work, one sample person and one sample fair

Ask each prospective provider to walk through the same three items: a work with a complex history, a collector with several roles and an upcoming fair. This is more revealing than a generic dashboard. You will see whether the system reflects the way your gallery works or asks the team to flatten it into unrelated lists.

Choose the history, not just the current state

A current status tells you where a work is today. The history tells you why. Both are useful, but only one helps a colleague reconstruct a decision made six months ago.

Look for a system that can connect an action to the records it affected: a price request, a PDF sent, a viewing, a reservation, a condition note or a fair conversation. The activity should not be treated as an optional comment bolted to a contact. It should be possible to see that it happened to a specific work, with a specific person, in a specific context.

This is where a generic contact manager often becomes awkward. It may be excellent at keeping names and tasks, but it does not necessarily understand the relationship between a work, an event and the person who encountered it. Conversely, inventory-only software can make a work look complete while leaving the conversations around it in scattered places.

For galleries considering a move from a legacy platform, the Artlogic migration overview explains the practical issue: useful information often lives in columns without a neat destination. Before choosing a replacement, list the fields your team has kept precisely because they have not found a better home.

Test the system against a fair, not a quiet Tuesday

A fair compresses the gallery’s operations into a few fast days. Works move. Prices are requested. Guests arrive. The team needs to know what is available, what is promised, what has been seen and what needs a follow-up. A system that feels clear in a tidy demonstration can become slow when several people make changes at once.

Ask to see how the platform handles the operational objects around the fair, not just the contact list. Can it hold a checklist, guest list and allocation in one place? Can a conversation at the booth be connected to both the visitor and the work? Can somebody prepare a follow-up list from those interactions without retyping notes?

If your programme revolves around fairs, this should carry more weight than a feature you will use twice a year. A gallery’s system earns its place by reducing the reassembly work that follows a dense event.

Make permissions specific enough to be useful

Access is not simply an administrative concern. It shapes whether people can use the system comfortably. A registrar may need a complete view of a work’s dimensions, location and documents. A freelancer may need a fair list. A junior colleague may need to prepare a proposal. None of those roles automatically requires price visibility or access to every commercial note.

Check whether permissions can follow the real responsibilities in the gallery. Ask what happens when someone changes roles, leaves the team or needs temporary access for a project. The answer should be clear enough to use without an exception process for every ordinary handover.

Plan the migration before committing

Migration is not a chore to save for after the contract is signed. It is the moment when the gallery decides what the new system will remember. A good provider will help you identify source records, retain useful IDs, test a representative sample and find the exceptions before they become production problems.

1. Map the source. List the exports, shared drives and active spreadsheets that hold the working record.
2. Choose representative samples. Include an uncomplicated work, a complex consignment, a repeat collector, a past fair and a document-heavy record.
3. Define what must survive. Current status, location, price rules, documents, dates, provenance and relationship history may all matter, but make the list explicit.
4. Test a second import. The team needs to know whether a correction updates the right record or creates a duplicate.
5. Agree the handover. Decide who checks exceptions and how people will work while the move is in progress.

Data portability deserves the same scrutiny. You should be able to understand what comes out of the system and how. A clear pricing and access model also helps the gallery separate the daily record-keeping it needs from advanced capabilities it may choose later.

Use the demo to resolve risk, not admire polish

A polished interface is pleasant. It is not yet evidence that the system will hold up under your programme. Prepare a short list of questions before the demonstration and insist on real answers. The best demo is not a tour of everything. It is a close look at the things that could make the move succeed or fail.

• Show us one work with an artist, documents, location, commercial status and prior activity.
• Show us how a fair changes what the team sees and does.
• Show us what each role can and cannot see.
• Show us how a corrected import behaves.
• Show us how we would export the records if we needed them elsewhere.

A provider that can answer these questions directly is giving you something more useful than a checklist. It is showing you whether the product has a coherent point of view about the gallery’s work.