I am currently in the planning stages of a monumental migration for our revenue operations team: moving from a two-decade-old, heavily customized Microsoft Access database that has been serving as our de facto CRM to a modern platform, likely Salesforce or HubSpot. The business logic woven into this Access "system" is profound, encompassing everything from lead scoring algorithms to commission calculations, all built via a labyrinth of VBA modules, linked tables, and macros.
My preliminary analysis suggests this will be less a traditional CRM migration and more a full-scale business process re-engineering project, with data extraction being merely the first hurdle. The core challenges I am modeling appear to be:
* **Documentation Void:** There is no entity-relationship diagram or data dictionary. Business rules exist only within the code and the institutional memory of two key employees nearing retirement.
* **Data Quality & Structure:** The database suffers from severe normalization issues. For example, customer notes are stored in a single memo field with a proprietary tagging system (e.g., "##CALL## 12/5/10: Discussed pricing..."). Parsing this for migration is non-trivial.
* **Integrated Processes:** The Access database doesn't just store data; it *is* the process. It generates PDF invoices, prints shipping labels directly to a warehouse printer, and feeds a separate reporting cube. These are all brittle, point-to-point integrations that will need to be rebuilt.
I am seeking insights from anyone who has undertaken a similar journey from a legacy, monolithic Access application to a cloud-based CRM. Specifically:
* Was your primary strategy a "lift and shift" of the existing logic, or did you use the migration as an opportunity to fundamentally redesign and simplify processes?
* How did you approach mapping and extracting the data? Did you find it more effective to write custom VBA extraction routines or to connect to the Access backend (likely JET/ACE) via another tool like Python or SQL Server Integration Services?
* What broke immediately post-migration that you didn't anticipate? I am particularly concerned about the loss of "hard-coded" business rules that no one ever thinks to document.
My initial risk assessment model shows a high probability of extended downtime and significant operational disruption if we proceed with a direct cutover. Any war stories or lessons learned on phased approaches, parallel running, or change management would be invaluable.
--JK
measure what matters