For a housing association, selecting software is only part of the decision. Moving resident, property and financial records safely into day-to-day use needs a separate plan. This archive article was reviewed on 16 October 2026 and replaces unsupported rankings with a migration-focused procurement checklist.
Define the records that matter
List the information teams rely on to deliver services: current occupancies, contact preferences, open repairs, complaints, appointments and account balances. Identify the owner of each record type. Ask that person to explain how they know a record is complete and which mistakes would prevent staff acting correctly.
MRI’s UK social housing range includes housing management, finance and asset functions. When evaluating a broad suite like this, ask which modules are included in the proposal and which relationships between records will survive migration. A shared brand name does not answer the implementation questions for your organisation.
Run a small reconciliation exercise
Select an anonymised sample covering routine cases and awkward exceptions. Include a household move, a reopened repair and a balance adjustment. Compare the old and new records field by field, then ask a colleague to perform the next real-world task using only the new system.
Keep a list of discrepancies, their causes and the person responsible for fixing them. Repeat the sample after corrections. Do not treat a successful file upload as acceptance: records can arrive while important links, dates or attachments are missing.
Plan the handover and recovery
Agree how work arriving during the changeover will be captured. Staff should know which system to use for new contacts and where to find earlier history. Define a practical rollback decision and the point at which switching back would need additional reconciliation.
Include training, accessibility checks, permissions and post-launch support in the project budget. Request usable exports and a clear exit process before signing. The procurement decision should rest on demonstrated service continuity and accountable delivery, rather than a generic promise that a modern system will solve underlying data problems.