Funeral homes are dealing with older software that was never meant to connect to anything else.
I have spent years watching funeral directors try to make legacy systems do things they were never designed for. The Thomson Funeral System came out of an era when a computer inside a funeral home mostly just printed contracts and kept basic records. It worked fine for that. The problem started when families began expecting websites, digital memorial pages, and the ability to share obituary information across platforms without picking up a phone. The Thomson system has been around long enough that most funeral homes using it have spent a decade building custom workflows around its limitations. I ran into a specific situation last year where a director needed to pull death certificate data from Thomson and push it to a third-party obituary platform at the same time. Thomson does not have an API. The data lived in a flat file export that had formatting quirks depending on which state the death occurred in. Some fields would drop characters if they exceeded a certain length, and dates came back in inconsistent formats depending on the individual entry. My workaround was to build a small script that read the exported CSV, normalized the date fields to a single format, trimmed fields to safe character limits, and then fed the cleaned data into the obituary platform's upload tool. It took about forty minutes to set up the first time. After that, the whole process took under ten minutes per case. What is actually reshaping end-of-life care right now is not any single piece of software. It is the slow accumulation of integrations between old funeral management systems and newer tools that handle memorial websites, grief support platforms, and digital legacy planning. Thomson Funeral System itself is not the thing doing the reshaping. It is the pressure that funeral homes feel to make it talk to everything else.
There is a misconception that modernizing a funeral home means replacing the core management system. That is usually the wrong first step. The cost of migrating years of case data from Thomson into a new platform is significant, and the risk of losing historical records is real. Most directors I know who have tried this regretted the migration. The smarter move is to treat Thomson as the system of record and build integration layers around it. A simple middleware approach using tools like Zapier or a custom Python script can pull data from Thomson exports and feed it into modern memorial and obituary platforms. This keeps your historical data safe while giving families the digital experience they now expect. One counter-intuitive detail that people miss is how much workflow friction actually comes from the system itself being reliable. Thomson is stable. It does not crash. But that stability means many funeral homes have not updated their processes in years because nothing broke. When you finally try to integrate it with a new tool, you discover that the export formats, field naming conventions, and data entry habits have drifted from standard practices over a decade of unchallenged use. Custom fields created by previous staff members often have vague labels like "Notes" or "Additional Info" that contain structured data in unstructured text. Parsing that reliably requires knowing who entered each field and why, which means talking to people who already left the business. Another thing beginners get wrong is assuming that a Thomson integration project is purely a technical problem. It is mostly a permission problem. The staff member who knows how the system is configured is often the director themselves, and they are busy handling cases. You need to schedule a proper audit of the current setup before writing any integration code. Figure out what fields are mandatory, what fields are optional, what custom reports are running, and what manual steps happen after data export. I have seen multiple projects stall because someone skipped this step and assumed the system was doing something it was not actually doing.
The limitations of Thomson Funeral System matter when you are planning any technology upgrade. It was never built for cloud-based workflows. There is no real-time sync capability. You are working with batch exports and imports, which means there is always a delay between the system and whatever external tool receives the data. If a funeral home handles fifty to a hundred cases per month, the export process becomes a recurring administrative burden. It is manageable, but it is not free. Also, Thomson's reporting module is limited compared to modern business intelligence tools. If your team needs custom analytics, you will be exporting raw data and building your own reports elsewhere regardless of whether you are integrating with other systems. For funeral homes that are heavily invested in Thomson and deal with a high volume of cases, the realistic path forward involves three parallel tracks. Maintain the core Thomson installation for daily case management and compliance documentation. Build or buy an integration layer that handles exports to obituary and memorial platforms. Invest in a separate practice management or CRM tool that serves as the modern front end while Thomson remains the back end database. This hybrid approach adds complexity, but it avoids the catastrophic data migration risk of a full replacement. I also want to be blunt about one scenario where this does not work at all. If your Thomson installation has accumulated years of inconsistent data entry, missing fields, and duplicate records with no cleanup process, no amount of integration middleware will fix that. You need to run a data quality audit first. Clean the data inside Thomson before you try to push it anywhere else. Doing it in reverse just spreads bad data into every connected system.
Get the Full Details
The people using Thomson Funeral System today are mostly the same funeral homes that adopted it twenty or thirty years ago. They are not going away. The ones adapting are treating the software as infrastructure rather than a solution, building lightweight connections around it instead of trying to replace it. That is the quiet reshaping happening in this industry, not a dramatic technology shift.
