Business Trip Report · System Migration

SHPOOOV Migration Business Trip Report

A clear mobile-first summary of the Riyadh onsite migration: data recovery, subscription correction, gate validation, InBody integration, staff training, and operational handover.

PeriodJun 3–9
LocationRiyadh
StatusHandover done
ReturnJeddah 11 PM
Executive summary

This was not just a migration. It became a full operational cleanup and go-live support effort.

The trip moved SHPOOOV from a legacy system with limited export options and inconsistent subscription data into a validated operating setup on the new system.

By the end of the trip, the club had migrated data, corrected subscriptions, validated gates, tested InBody integration, trained staff, and a clear remote follow-up path.
View daily journey
Impact at a glance

What changed

7days from discovery to handover
160subscription cases resolved programmatically
42conflicting records corrected and closed
5+Excel reports delivered for validation
6 AMlate access-control validation shift
11 PMreturned from Riyadh to Jeddah
Completed workstreams

End-to-end operational readiness

1
Legacy data extractionBuilt a scraping approach because the old system had no direct export.
2
Member migrationCleaned and uploaded member records into the new system.
3
Subscription correctionFound and fixed major inherited inconsistencies using invoices as source of truth.
4
Gate validationValidated the biometric device → local bridge → backend access-control path.
5
InBody integrationCompleted and tested the InBody integration.
6
Training and handoverTrained the team, improved UX flows, and handed over for operation.
Daily journey

What happened each day

Wednesday · June 3

Travel and legacy-data extraction

Arrival in Riyadh around 9:30 AM
  • Inspected the legacy system and how customer data was stored.
  • Built a quick scraping tool because there was no direct export.
  • Started extracting customer records and cleaning data after hours.
Thursday · June 4

Member migration and subscription preparation

Onsite 2:00 PM–6:00 PM
  • Uploaded all member records to the new system.
  • Extracted and cleaned subscription data for migration.
  • Identified invalid phone numbers and non-Saudi registration considerations.
  • Provided the club with a clean organized Excel customer file.
Friday · June 5

Subscription migration and access-control investigation

Second shift continued until 6:00 AM Saturday
  • Completed subscription migration as a practical quick win.
  • Investigated gate and biometric-device restrictions.
  • Validated the working path: biometric device → local network → local bridge → backend.
Saturday · June 6

Gate validation and critical findings

8:00 PM–2:00 AM Sunday
  • Validated that the gate flow was operational.
  • Discovered 160 six-month subscriptions with incorrect 2028 end dates.
  • Discovered 42 cases with conflicting subscription records.
  • The findings changed the return plan and required continued onsite work.
Sunday · June 7

Reports, invoices, and first correction wave

8:00 AM–8:00 PM onsite
  • Prepared more than five Excel reports explaining the issues and correction approach.
  • Helped classify paper invoices as valid source of truth.
  • Corrected the 42 conflicting cases one by one and closed that file.
Monday · June 8

Programmatic fix for 160 subscriptions

8:00 AM–11:00 PM onsite

Instead of manually correcting 160 records, the correction was calculated programmatically using electronic invoice data, amount paid, and subscription start date.

Problem160 incorrect end dates from legacy data.
ActionCalculated correct end dates from invoice evidence.
ResultClub team validated only. File fully closed.
Tuesday · June 9

Training, UX improvement, InBody, and handover

9:00 AM–6:00 PM onsite
  • Trained the club team on the new system.
  • Observed real usage and solved UX issues as they appeared.
  • Improved the flow so work could be completed without jumping between unrelated pages.
  • Completed and tested InBody integration.
  • Handed over the system for operational use.
  • Returned from Riyadh to Jeddah around 11:00 PM.
Memories

A few field-trip moments

A small scrapbook from the onsite migration journey: system walkthroughs, invoice validation, bridge debugging, gym environment checks, and the long-fieldwork moments behind the handover.

System walkthrough at the club
System walkthrough with the club team
Paper invoices and validation documents
Invoice validation source of truth
Bridge and backend logs on screen
Bridge and backend debugging
SHPOOOV gym mural
SHPOOOV onsite environment
Company colleague moment
Company colleague moment during the trip
Terminal logs during bridge operations
ADMS bridge log monitoring
Dinner during onsite work
Late onsite dinner break — the steak that kept the migration alive.
Final onsite status

The system was handed over for operational use.

Ready for daily operationThe club team was trained and the system was handed over after real-usage validation.
Operational flow improvedUX issues were fixed so the team can complete tasks in a continuous journey.
InBody completed and testedInBody operations were connected as part of the new setup.
Remote follow-up

What remains after the trip

The remaining scope is remote follow-up and app launch coordination after Abo Rabiah returns from India.

App launch timingLaunch the app after Abo Rabiah returns from India, expected around June 15–16.
Monitor payment usageCheck whether the club is using offline or online payment flows and confirm operations are stable.
Final small migrationOne small migration remains pending until the club provides missing information.
Feedback loopCollect feedback from the team and resolve issues that appear during real usage.

Generated for SHPOOOV migration activities, June 3–9, 2026.