Promsoc Brussel — Student Association Platform Rebuild
Full platform rebuild for a Brussels-based student association — legacy system modernisation, zero-loss migration of 10,000+ user records, multilingual support, and a scalable course registration system built to handle 100,000+ users.
Visit site- CLIENT
- Promsoc Brussel
Brussels, Belgium - ROLE
- Full Stack Engineer
- DURATION
- 6 months
- TEAM
- Solo
10k+
User records migrated with zero data loss
100k+
Users supported after rebuild — up from a system that failed under hundreds
25%
System performance improvement over legacy baseline
Tech Stack
- Laravel
- Laravel Nova
- Vue.js
- Alpine.js
- Livewire
- Tailwind CSS
- MySql
- Redis
- AWS EC2
- AWS S3
- Cloudflare
- Forge
- Google Analytics
- Figma
Delivery
PHASE 01
Discovery & Flow Mapping
Conducted structured workshops with the Promsoc team to map every user-facing workflow end to end — registration, membership renewal, course enrolment, payment, and admin approval. Identified all system actors (members, administrators, course coordinators) and verified which flows communicated directly with the client before any build decisions were made.
PHASE 02
MVP Build & Client Validation
Built a focused MVP covering the core member registration and course enrolment journey. Walked the client through the working prototype, gathered structured feedback, and iterated on layout, language, and logic before expanding scope — preventing rework on peripheral features before the foundation was solid.
PHASE 03
Full Feature Build
Built out the remaining functionality required to run the complete operational workflow: admin dashboard, bulk enrolment management, payment reconciliation, role-based access control, automated confirmation emails, and the multilingual content layer. Every feature was developed against the verified flow map from Phase 1.
PHASE 04
Go-Live & Handover
Coordinated a phased go-live to allow the client team to begin using the new platform while the migration pipeline ran in parallel. Delivered support documentation and a walkthrough session so the Promsoc team could operate the system independently from day one.
PHASE 05
Post-Launch Improvements
Worked through a structured backlog of client-requested enhancements — refined reporting views, additional notification triggers, bulk import tooling for new course records, and accessibility improvements identified through real member usage. All changes deployed incrementally to avoid disruption to active users.
Outcomes
- Platform now supports 100,000+ concurrent users — rebuilt from a system that failed under a few hundred simultaneous sessions.
- Overall system performance improved by 25% against legacy baseline benchmarks.
- Full responsive support across mobile, tablet, and desktop — mobile usage increased significantly post-launch with zero layout regressions.
- Multilingual support (French, Dutch, English) across every member-facing surface — language-related support requests dropped to zero.
- Zero data loss across the full migration of ~10,000 user records and their complete course registration histories.
Challenges & Learnings
Migrating 10,000 users from a legacy system — without losing a single record.
Close to 10,000 user accounts — along with their full course registration histories, payment records, and membership status — needed to be transferred into a completely different data model. The legacy system had no formal API and inconsistent data formatting accumulated over many years. The solution was a dedicated migration pipeline that extracted raw data from the legacy database, applied a staged transformation and validation process, and loaded records into the new schema only after each record passed a full set of integrity checks. A reconciliation report was generated after every run, comparing record counts and key field values between source and destination. The pipeline was run multiple times in a staging environment with the client verifying sample records at each stage before the production cut-over was approved.
Rebuilding a live platform without disrupting an active membership.
The rebuild had to be delivered without forcing members off the old system mid-cycle or losing any in-flight registrations during the transition window. The approach was to develop and validate the new platform in full isolation, run both systems in parallel during the final migration phase, and coordinate the cut-over to a low-activity window confirmed with the client. A rollback path was kept available until the reconciliation report confirmed full data integrity on the new system.