IT that protects the catalog, every donor record, decades of archives.IT that protects thecatalogeverydonorrecorddecadesofarchives
Collections, archives, donors and visitors supported by IT that respects both a lean budget and an irreplaceable mission.
Vault, galleries and office
Some of what you hold can’t be replaced
Museums keep objects, and increasingly the knowledge about those objects lives in software: catalog records, conservation reports, provenance research and image libraries. Alongside it sit donors, members and visitors whose trust funds the mission. Here’s how cultural institutions get hurt, and how we help them hold on to what matters.
01 · The pressure
The catalog is the institution’s memory
Registrars track every object, loan and condition report in the collections management system. Digital archives hold high-resolution photography, scanned letters and oral histories. Development staff manage donors, pledges, grants and the gala auction in a CRM. Visitor services runs timed tickets and memberships, and the museum store takes cards. If ransomware encrypts the file server, you lose more than a week of work: decades of research notes, image rights records and loan paperwork may be gone if backups weren’t isolated.
- Collections records hold provenance and loans
- Image archives represent years of photography
- Donor CRM funds the whole mission
TessituraBlackbaud AltruBlackbaud Raiser’s Edge NXTTMS CollectionsPastPerfectAxiell Collections
02 · How it breaks
Lean IT, shared logins, open archives
Cultural institutions often run on a part-time IT person, a vendor or a volunteer with good intentions. Shared accounts for interns and docents never get removed. A development officer is phished, and the donor database is exported. A grant-funded digitization project leaves terabytes of images on an external drive with no second copy. The building management system and environmental sensors share a network with public Wi-Fi. And backups sit on the same server ransomware would encrypt.
- Intern and docent accounts never removed
- Donor database exported after phishing
- Backups stored right next to the originals
TessituraBlackbaud AltruBlackbaud Raiser’s Edge NXTTMS CollectionsPastPerfectAxiell Collections
03 · What we change
Isolated backups, named access, split networks
Collections databases, digital archives and the file server get versioned backups with an offsite, immutable copy that ransomware can’t reach, plus restore tests you can watch. Staff, interns, volunteers and contractors get named accounts with roles and end dates. Development and finance get MFA and impersonation filtering. We separate networks for staff, collections systems, the museum store, building and environmental controls, and public Wi-Fi, and we coordinate with your facilities contractor on controller access.
- Immutable offsite copies of archives
- Named accounts with end dates for volunteers
- Building controls apart from public Wi-Fi
TessituraBlackbaud AltruBlackbaud Raiser’s Edge NXTTMS CollectionsPastPerfectAxiell Collections
04 · The after
Show your board and funders a plan
If something goes wrong, the catalog and archives come back from a copy that wasn’t touched. Volunteers and interns get the access they need for their season and lose it when they leave. Donor data stays inside a CRM with MFA and logged exports. When a funder, lender institution or insurer asks how you protect collections data and personal information, you hand over a short written plan. And your small staff spends its time on exhibitions, not on recovering files.
- Archives restorable from untouched copies
- Volunteer access ends with their season
- A written plan for funders and lenders
TessituraBlackbaud AltruBlackbaud Raiser’s Edge NXTTMS CollectionsPastPerfectAxiell Collections