01 / 01
Shomre Hadas
The live Shomre Hadas public website; the operational migration work itself remains private.
← Business portfolio
Automation / Migration programme
Shomre Hadas
Give legacy data a new home.
DEVELOPMENT RECORDED
2026
Development recorded in the project repository. Earlier work may predate this history; this is not a confirmed launch date.PROJECT TYPE
Automation
BUILT WITH
THE SCREENS BEHIND THE SYSTEM
1 screenInside Shomre Hadas
The live Shomre Hadas public website; the operational migration work itself remains private.
Shomre HadasFull size ↗
The problem
A community organisation had outgrown a legacy Access database but still depended on it for people, families, marriages, subscriptions and billing. Moving to Zoho CRM meant rebuilding the organisation's working relationships and financial meaning, not merely copying rows into a newer screen.
Staff continued using the old system during the programme, so the target kept moving after the first transfer. Legacy identifiers had to survive, later changes needed reconciliation and unpaid invoices had to remain distinct from work that had not yet been billed.
The solution
The staged migration programme redesigns the legacy model as connected Zoho CRM modules, preserves the original identifiers and validates how people, households, relationships, subscriptions and finance reconnect in the new operation.
Delta synchronisation and cross-system comparisons identify changes after the initial move instead of overwriting them blindly. Financial work keeps invoiced balances separate from future billing work. Parts of the programme are complete and further modules remain 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