Shomre Hadas
Give legacy data a new home.
Automation
The problem
Moving an Access system into Zoho CRM is not a flat export. People, families, marriages, subscriptions and billing relationships use different structures in the two systems. Legacy identifiers need to survive, and staff continued changing the old system after the initial migration.
Financial reconciliation adds another distinction: an unpaid invoice is not the same as an amount that has not yet been charged. Combining those categories would carry the wrong meaning into the new system.
The solution
The migration programme maps the legacy relationships into CRM modules, retains original identifiers and reconciles changes made after the first transfer. Cross-system comparisons provide a way to identify drift instead of assuming the initial import remained current.
Financial work distinguishes invoiced balances from future billing work. Migration and delta synchronisation are complete for parts of the system, with further modules still in progress.
The decisions behind it
- Preserve meaning, not just columns
- A family billing unit, an individual and a relationship between people need separate mappings that still reconnect correctly in the CRM.
- Migration is a moving target
- If staff keep using the old system, changes after the first import need reconciliation rather than a second blind copy.
- Debt versus work to bill
- Outstanding invoiced money and charges not yet raised must remain different categories.
- Member and family record migration
- Legacy relationship mapping
- Post-migration change reconciliation