Case studies

CardOffice in production

A card programme cannot pause while its software is replaced. This is how one card office moved two decades of records across in a day, with the numbers. It is the first case study, and more will follow as customers agree to be written about.

Tertiary education

A 20-year legacy card system replaced in one day

How the card office behind a New Zealand tertiary institution moved 12,500 cardholder records off an on-premises SQL Server database, with no pause in issuing, no inbound firewall rule and no issue-number drift.

  • 12,703 of 12,703 source rows accounted for at cutover
  • One day: rehearsed on a restored copy in the morning, live by evening
  • Two-way sync keeps the old system current, so nothing hinged on a switch-off date
Your own system

Your migration, planned before you commit

Whether you are moving off desktop card software, a database nobody will expose, or a spreadsheet that has outgrown itself, the cutover is designed around what you cannot stop doing.

  • Outbound-only agents: no inbound firewall rule to ask your IT team for
  • Rehearsed first: run against a restored copy before the real thing
  • Reconciled by count: every row taken, and every row held back, accounted for

Talk to someone who has done this before

Tell us how you issue cards today and we will show you what the migration plan would look like for your institution.

Book a consultation