JCMS Was Discontinued — What Now?

For nearly two decades, the Jackson Laboratory Colony Management System (JCMS) was the gold standard for rodent colony management in academic research. Developed with NIH funding and distributed freely to qualified institutions, JCMS gave labs a structured way to track animals, breeding pairs, genotypes, and pedigrees. Then, in 2015, Jackson Laboratory quietly announced it would no longer maintain or distribute the software. For thousands of labs, the question became: what now?

A brief history of JCMS

JCMS began as an internal tool at The Jackson Laboratory in Bar Harbor, Maine, during the late 1990s. As transgenic mouse research exploded, labs needed a way to track increasingly complex breeding schemes, multi-allele genotypes, and Mendelian inheritance patterns. JCMS filled that gap with a desktop Java application backed by a Microsoft SQL Server database.

NIH grants funded JCMS development and allowed Jackson Lab to distribute it at no cost to academic institutions. At its peak, hundreds of labs across North America relied on JCMS as their primary colony management tool. The system handled cage tracking, animal records, breeding management, genotyping workflows, and basic reporting.

Why JCMS was discontinued

The decision to discontinue JCMS was not sudden. Several factors converged over the years:

• Funding dried up. NIH grants that supported JCMS development were not renewed. Without sustained funding, Jackson Lab could not justify a dedicated development team for a free product.
• Technology aged out. JCMS was built on Java Swing and Microsoft SQL Server — technologies that became increasingly difficult to support across modern operating systems. Labs running macOS or Linux were effectively excluded.
• Support was unsustainable. As a grant-funded project, JCMS never had a commercial support team. Bug reports went unresolved, and feature requests piled up with no roadmap.
• Cloud expectations changed. Researchers began expecting web-based tools they could access from any device. JCMS required local installation and a dedicated database server — a significant IT burden.

What happened to JCMS users

When JCMS was discontinued, existing users were left in a difficult position. Some labs continued running their aging JCMS installations for years, accepting the risk of unsupported software on outdated Java runtimes. Others attempted to export their data, only to discover that JCMS's complex relational schema made migration painful.

Many labs simply went back to Excel. The regression was immediate: breeding records became disconnected from animal records, pedigree tracking was abandoned, and IACUC reporting once again required hours of manual counting. A decade of data management progress was undone.

The case for commercial colony software

The JCMS story illustrates a fundamental problem with grant-funded research tools: they depend on continued funding. When grants end, the software dies — regardless of how many labs rely on it.

Commercial colony management tools take a different approach. By charging a sustainable subscription, they can maintain dedicated engineering teams, provide ongoing support, and continuously improve the product. The software survives because the business model supports it, not because a grant committee renewed the funding.

This does not mean commercial tools need to be expensive. Many labs operate on tight budgets, and the best colony software recognizes this with free tiers for small labs and affordable plans that scale with colony size.

Modern alternatives to JCMS

Today, labs migrating from JCMS (or from the Excel they fell back to) have several options:

• SoftMouse.NET — A web-based colony management tool that has been available since the JCMS era. It offers comprehensive features but at a price point that can be prohibitive for smaller labs.
• PyRAT — Popular in European institutions, PyRAT provides detailed animal tracking and compliance features. It requires an institutional server installation.
• ConductColony — A modern, cloud-native colony management platform built for labs that have outgrown spreadsheets. Free for small labs, with breeding, genotyping, and pedigree visualization on paid plans.

How to migrate from JCMS

If your lab still has JCMS data — whether in a running installation or an old SQL Server backup — migration is straightforward:

1. Export your animal, cage, and breeding data to CSV files. JCMS supports direct CSV export from its reporting module.
2. Clean up the data. Remove inactive animals, retired cages, and duplicate records. This is also a good time to standardize strain names and genotype nomenclature.
3. Import into your new platform. Tools like ConductColony include a CSV import wizard that maps your columns automatically and handles strain, cage, and animal creation in a single step.
4. Verify your data. Spot-check a sample of animals, confirm breeding pair assignments, and ensure protocol associations transferred correctly.

Looking forward

The discontinuation of JCMS was a loss for the research community, but it also created an opportunity to rethink how colony management should work in the modern era. Cloud-native platforms, AI-powered data import, pedigree visualization, and real-time IACUC compliance tracking are all features that JCMS could never have delivered.

If your lab is still managing colonies in Excel — or running a decade-old JCMS installation — it may be time to explore what modern colony software can do.