How MGH Neuroscience Replaced Excel with ConductColony

The Challenge

The neuroscience laboratory at Massachusetts General Hospital maintains a transgenic mouse colony of approximately 320 animals across 12 strains, including several conditional knockout lines used in Alzheimer's and Parkinson's disease research. The colony is managed by a team of four: a principal investigator, a lab manager, and two research technicians.

For years, the lab tracked its colony in a shared Excel workbook stored on a departmental network drive. The workbook had grown to over 20 tabs — one for each strain, plus tabs for breeding pairs, genotyping results, cage assignments, and IACUC protocols. The system worked when the colony was small, but as the lab expanded its transgenic lines and added personnel, cracks began to show.

Data loss was the most painful problem. On two separate occasions, a team member accidentally deleted rows containing months of breeding records. The network drive had no version history, and the lab's backup policy covered only nightly snapshots — meaning any changes made after the morning backup were at risk. After the second incident, the PI spent a weekend reconstructing breeding records from handwritten cage cards and laboratory notebooks.

IACUC compliance was the second major pain point. Preparing for the semi-annual review required the lab manager to manually count all animals on each active protocol, cross-reference protocol numbers with animal IDs across multiple tabs, and produce a census report. This process consistently took two full working days — time that could have been spent on research.

Finally, pedigree tracking had become untenable. The lab's conditional knockout lines required crossing Cre-expressing animals with floxed allele carriers, producing offspring that needed to be genotyped for two independent alleles. Tracing an animal's lineage back through three generations to verify correct breeding required manual lookups that were slow and error-prone. On at least one occasion, a genotyping error was traced back to a mis-recorded parent ID in the spreadsheet — an error that invalidated three months of experimental data.

The Solution

The lab manager discovered ConductColony while searching for JCMS alternatives. After a brief evaluation of the free tier, she presented the tool to the PI, who approved a trial migration.

The migration process took a single afternoon. The lab manager exported the master Excel workbook as CSV files and uploaded them into ConductColony's import wizard. The wizard automatically detected column mappings — recognizing "M/F" as sex values, parsing mixed date formats, and normalizing strain abbreviations like "B6" to their official JAX nomenclature (C57BL/6J). After reviewing the preview and confirming the mappings, all 320 animals, 85 cages, 12 strains, and 3 active protocols were imported in a single operation.

The team began using ConductColony the next day. Each team member created an account with magic link authentication — no passwords to manage. The lab manager set up role-based permissions: technicians could add and edit animals but not delete protocols or modify billing settings.

Breeding pair management was the feature that made the biggest immediate impact. The lab created breeding pairs directly in the system, linking sires and dams to specific cages. When litters were born, technicians recorded pup counts and dates on the same screen. Genotype results were entered using batch entry — selecting multiple weanlings and assigning allele status in a single form submission.

The 3-generation pedigree viewer became the lab's go-to tool for verifying experimental animals. Before including any mouse in an experiment, the technician would check its pedigree to confirm both parental alleles were correctly transmitted. The visual tree made inheritance patterns immediately obvious — no more tracing IDs through spreadsheet rows.

The Results

After three months of using ConductColony, the lab documented the following improvements:

• IACUC preparation time dropped from 16 hours to under 2 hours. The census report — previously assembled manually from multiple spreadsheet tabs — was now generated instantly from the dashboard. Protocol associations, animal counts by species and strain, and pain category breakdowns were all available with a single click.
• Data entry errors were eliminated. The activity log tracked every change with a timestamp and user attribution. When a technician accidentally modified a cage assignment, the lab manager spotted the change in the log and corrected it within minutes. No data was lost.
• Genotyping accuracy improved significantly. The pedigree viewer caught two potential parent-offspring mismatches that would have gone unnoticed in the spreadsheet system. Both were corrected before any animals were used in experiments.
• Multi-user access was seamless. All four team members worked in the system simultaneously without file locking, merge conflicts, or version confusion. The lab manager no longer needed to serve as the single point of data entry.

What the PI says

"We should have made this switch years ago. The breeding records alone justify the subscription — but what really sold me was the pedigree viewer. Being able to verify lineage at a glance, instead of tracing IDs through a spreadsheet, has materially improved the reliability of our experimental cohorts. And the IACUC census? What used to take two days is now instant. I honestly cannot understand why any lab would still use Excel for this."