A CRM is only as powerful as the data behind it, and for many organizations, that data is trapped in legacy structures.
In my previous post, I explored why a native CRM is a more robust solution than forcing nodes to manage relationship data. The positive response from the community was immediate. However, while the vision for Drupal CRM is clear, the practical challenges of tech-debt remain.
In order to truly move off the “Drupal Island,” we must provide clear pathways for data to flow both into and out of the system.
Free data to avoid vendor lock-in
It is not enough to get data into a system; you must be able to get it out. One of the primary fears of any platform change is “vendor lock-in.” To address this, Drupal CRM needs to leverage the full power of Drupal’s web services.
As I was reviewing the Comparison of CRM modules to determine which system we should migrate next, I realized that I overlooked how to deal with contacts stored as nodes. Doh! Since ‘node’ is not a brand name, there is no listing for it on the comparison. I even wrote a blog post about nodes being used as ad-hoc solutions.
So, recognizing that people are storing contacts as nodes and realizing we need to meet people where they are, I knew a better way is irrelevant if there is no path for others to follow. Leaders look after their followers. And so I spent a day creating the Migrate Node to Drupal CRM project. There will be improvements, but it is complete and ready for people to use.
By utilizing JSON:API and the REST module, the data remains portable and accessible. For those needing specialized reporting, the REST Views module allows for seamless integration with external tools like Microsoft Power BI.
We are investigating how we can adhere to Schema.org standards. This will allow Drupal CRM to better integrate with external systems by structuring the data in a way that external systems already understand. We aren’t just providing one path to get your data out, we want to provide many paths.
Building the bridge with migration pathways
A native CRM only gains value when it is populated with high-quality data. Recognizing this, we are focusing heavily on the Migrate Node to Drupal CRM project. For organizations that have spent years building custom CRM-like structures using nodes, they now have a tool that maps legacy nodes to new contacts, and migrates the data with no programming, all configured within the UI. We wanted to provide the Drupal community an exit strategy from technical debt towards a standardized architecture.
The momentum doesn’t stop with internal migrations. We are seeing a network effect as developers create pathways from external and legacy systems. You can now migrate to Drupal CRM from: CRM Core, RedHen CRM, and OnePage CRM.
As more projects consider adopting Drupal CRM as a dependency, we are seeing a shift in the ecosystem. Instead of building fragmented, custom solutions, developers are contributing to a single, powerful core that benefits everyone.
We are thrilled that organizations like Fox Valley Drupal are migrating to Drupal CRM.
MidCamp is also considering migrating to Drupal CRM for MidCamp 2027. Buy your ticket for MidCamp 2026 today!
Community momentum in 2026
The spring of 2026 marks a significant milestone for the Drupal community–25th Anniversary of Drupal! As we celebrated at DrupalCon Chicago in March, the focus was squarely on sustainability and professional-grade tools. Drupal CRM fits that bill.
Join us
As mentioned above, regional events and meetups are already beginning to pilot Drupal CRM. The interest in Drupal CRM is undeniable, with many academic institutions and regional camps currently in the evaluation and planning phases. Drupal CRM needs your input and support. We thank you for your interest and invite you to join our effort.
- If you run a Drupal event, reach out.
- If you run a Drupal agency, reach out.
- If you are a Maintainer on Drupal.org and your project needs contacts, reach out.
Learn more
- My Journey Toward a Native Drupal CRM: And why nodes aren’t the answer for contact relationship management, by Steven Ayers
- Drupal CRM details page
- Drupal CRM – Contact Relationship Management project page
- Contact GovWebworks to learn more about our Drupal services
