Daad Journal — field notes on enterprise systems
Notes from inside the implementation.
What we learn selecting, migrating and supporting ERP, campus and HR platforms — written by the consultants doing the work, not a marketing team.
- Posts
- 8
- Topics
- 7
- Reading
- 63m
Posts
Topics
Reading
7 of 7 posts
- 02The data migration checklist we run before every go-liveEleven checks between a passing test migration and a live cutover. Skipping any one of them has cost someone a weekend.Implementation29 Jul 26→
- 03Campus timetabling at scale: constraints, not calendarsTimetables break because institutions model them as calendars. Modelled as constraints, they become tractable — and negotiable.Education14 Jul 26→
- 04What an HR department needs before it needs softwareBuying an HRMS to fix an undefined HR function produces a faster version of the same confusion. Four things come first.HR2 Jul 26→
- 05Backup capacity planning, in plain arithmeticRetention policy, change rate and recovery objectives are one calculation. Most organizations have never written it down.Infrastructure18 Jun 26→
- 06Training the second line: who actually keeps the system runningPower users get trained. The people who inherit the system eighteen months later usually do not — which is when platforms quietly decay.Training5 Jun 26→
- 07Azure landing zones for public-sector tenantsSubscription design, identity boundaries and policy guardrails, arranged so an audit is a report rather than an excavation.Cloud21 May 26→
- 08Reading a vendor's integration promisesSix questions that turn "fully integrated, API-first" into something you can put in a contract.ERP9 May 26→
Subscribe
One note a month. No product news.
Implementation write-ups, migration checklists and training material as we publish them.