Existing CMS vs Raisd portals — feature comparison

Document: SDD-14
Status: Working draft
Date: 23 September 2026 (updated 3 October 2026)
Source package: CMS_Cyberjaya_Source_Codes_&_DB_Structure_23_09_2026.zip Also inventoried: - Lesotho pilot (3 Oct 2026): newer-CMS screenshots + old dump pending → docs/ai/backend/old-cms-lesotho.md, approach docs/ai/architecture/lesotho-pilot.md - ICA_SierraLeone_Codes_&_DB_Structure_23_09_2026 → docs/ai/backend/old-cms-sierra-leone.md, Pages docs/diagrams/old-cms-sierra-leone/ - CMS_Botswana_Source_Codes_&_DB_Structure_24_09_2026 → docs/ai/backend/old-cms-botswana.md, Pages docs/diagrams/old-cms-botswana/ (E2E + DTEF §4), botswana-dtef-scholarship-sync.md Canonical detail (agents): docs/ai/backend/cms-feature-comparison.md, docs/ai/backend/old-cms-cyberjaya.md GitHub Pages (diagrams): docs/diagrams/old-cms/ — Comparison · FSD · Obsidian 3D · Legacy ERD · Flows · Database tech

1. Purpose

Record what the existing Cyberjaya CMS already does, and how that maps to the Raisd Applicant / Student / Lecturer / Staff portals and CAP catalogue (SDD-11).

This is an inspection baseline for gap decisions. It does not authorise replacing working legacy staff functions (SDD-01, ADR-1).

2. Framing

Side	What it is
Old CMS	Live campus system of record (`cmscbj`), PHPMaker desks + Laravel payment/PDPA, batch jobs, ~1.9k tables, ~318 procedures
New stack (this phase)	Four role portals + Portal API on top of that SoR — do not duplicate operational desks
Longer-term target	Progressive unified one-stop CMS, only via verified gaps + migration strategy (M5+)

This phase:   Applicant / Student / Lecturer / Staff  →  Portal API  →  Existing CMS (SoR)
Later:        Verified gap + migration plan  →  consolidate into unified CMS progressively

Working Group (23 September 2026 — Aslam): agreed this-phase posture (CMS as SoR, portals via Portal API, no duplication of operational functions). Longer-term unified CMS remains the aim, delivered progressively.

Working Group (3 October 2026): first pilot / acceptance campus is Lesotho. Cyberjaya remains the richest technical inventory for the LUCT PHPMaker family; Lesotho newer CMS (screenshots) is the feature benchmark for M4.

3. Headline findings

Staff operations are already broad in the old CMS: Registry, Faculty, Bursary, Marketing, Student Services (visa/medical/insurance), Accommodation, AQA/CDU, Library, Reporting, Lecturer Portal, LEC, Training, ICU PDPA, Payment.
Most Admin/Staff CAP rows have an old-CMS home. Default delivery rule remains: verify and reuse; build Raisd staff screens only for proven gaps (SDD-07).
Student Demo screens largely have matching CMS records (profile, registration, timetable, attendance, finance, documents, questionnaires, visa data). Live requires Portal API mapping (CAP-53), not a second database.
Applicant and Lecturer Raisd apps are behind the old CMS: online application + agent procedures and Lecturer Portal 1.0 already exist.
Malaysia regulatory desks (EMGS, KDN/MPWA, eIPTS, MQA/KPT) are rich in the old CMS and mostly out of scope for early Raisd screens — keep them operational on existing desks.
Clearer Raisd-led gaps: mobile shells, portfolio/resume, modern quiz/messaging productisation, unified helpdesk UX, and the Portal API contract itself.

4. Module → portal ownership

Old CMS module	Natural Raisd surface	Default action
Marketing + Registry applications	Applicant + Staff (Registry)	New applicant UX; keep decisions on CMS
Registry / SIU / studentrecords / stdfile	Student + Staff (Registry)	Student read/update via API; staff on CMS
Faculty + lecturer	Lecturer + Staff (Faculty)	Verify Lecturer Portal 1.0 before rebuild
Bursary + payment	Student finance + Staff (Bursary)	Ledger stays on CMS
Services (SSD/visa)	Student immigration + Staff	Ops on CMS; student view via API
Accommodation	Student housing + Staff	Allocation on CMS
CDU / AQA	Staff (QA)	Keep on CMS; CAP-04 evidence
Library	Student CAP-31 + Staff	Keep licences on CMS
ICU / PDPA	Shared CAP-39	Keep compliance on CMS
Reporting / training / lec	Staff / campus-specific	Usually no Raisd rebuild

5. Capability summary (by group)

Full CAP rows live in the AI comparison doc. Group posture:

Group	Old CMS	Raisd software	Posture
Applicant (8 CAPs)	Online app + docs + agent SPs Present/Partial	Not started	Build applicant portal on CMS data
Student (41 CAPs)	Records Present for core; LMS-style Partial	Demo / Partial / Placeholder mix	Map Demo → CMS; keep SoR
Lecturer (19 CAPs)	Lecturer Portal 1.0 + Faculty Present	Not started	Verify before new UI
Admin / Staff (38 CAPs)	Desk suite Present	Not started	Gaps only
Shared (6 CAPs)	Backups scripts Present; monitoring Needs checking	CAP-53 Partial / Needs checking	Integration critical path

6. What stays on the old CMS (unless later decided)

Agent management and agent claims
LEC / English Centre operations
Board / Senate / heavy regulatory reporting
Inventory, smart card, parking collection details
Nightly bursary / attendance / portal-login batch logic
Official transcript printing and graduation gown fee setup

7. Critical path for Live (this phase) and target delivery

This phase (M1–M4)

Confirm admissions staff can complete offer → first enrolment on old CMS (or document the gap).
Deliver CAP-53 first slice: auth + applicant create/read + document metadata acknowledgment.
Only then promote student Demo journeys that mutate registration or finance.
Do not mark any CAP Live from frontend Demo alone.
Do not rebuild working staff desks — Portal API + verified old CMS.

Target delivery snapshot

Horizon	Delivery target	SoR
M2 Admissions launch	Applicant portal + Registry workflows	Existing CMS
M3 Core student portal	Student journeys + lecturer/staff support paths	Existing CMS (or verified old desk)
M4 Lesotho pilot	Integrated acceptance, training, ops	Existing CMS + Portal API; Lesotho newer CMS as feature benchmark
M5+ Expansion / remaining CMS	Multi-campus + progressive consolidation	Migrate domain-by-domain only with a written strategy

High-level comparison pages: docs/diagrams/old-cms/comparison.html, agent matrix docs/ai/backend/cms-feature-comparison.md. Milestones: SDD-03.