CEUS SOLUTIONS — MIGRATION REVIEW OUTLINE ---------------------------------------- Project planning guide · 22 September 2026 ---------------------------------------- This outline describes requirements to scope and verify. It is not a completed client report, certification or proof that controls are deployed. Agree providers, owners, costs, exclusions and acceptance evidence for your project. ---------------------------------------- 1. DECIDE EXACTLY WHAT NEEDS TO MOVE Data profiling · Dependency analysis · Source inventory Start with one real task, such as taking an order, and follow the records it depends on. CHECKS - List the source system and version, available exports and who can authorise access. Profile a redacted sample for data types, missing values, duplicate keys and record volumes before committing to compatibility, cost or a date. - Choose the records in scope: customers, suppliers, item codes, stock by location, open orders, invoices, payments and attachments. Decide how much completed history must move or remain searchable. - Identify links to accounting, ecommerce, payment or other systems. For paper, spreadsheets and WhatsApp records, agree who enters or extracts the information, how it is checked and the cost. BEFORE SIGN-OFF Your team agrees what moves, what stays, who owns each source and which vendor permissions or export fees are needed. A missing export is resolved before the move is promised. WHAT YOU RECEIVE A source-and-record inventory with volumes, exclusions, dependencies and migration responsibilities. ---------------------------------------- 2. MAP THE FIELDS AND AGREE CLEANUP RULES Schema mapping · ETL · Deduplication Record how each old field becomes a usable record in the new system. CHECKS - Document the extract, transform, load (ETL) process: read the source, apply approved transformations and load the destination. Map customer, supplier and item IDs, preserving links between orders, invoices and payments. Item code 00125 must not silently become 125. - Agree date formats, time zones, currencies, decimal precision and units such as boxes versus individual items. Define what happens to blank fields, inactive records and unsupported values. - Review suspected duplicates with your team before merging or deleting anything. Keep an original source copy under the agreed retention policy and record each approved transformation. BEFORE SIGN-OFF A sample containing awkward cases, such as duplicate names, partial payments and different stock units, produces the result your team expects. WHAT YOU RECEIVE An approved field-mapping document, cleanup decisions and a list of unresolved records with owners. ---------------------------------------- 3. RUN A PROTECTED TRIAL IMPORT Staging environment · SHA-256 · Idempotent imports Rehearse the move in a separate environment while your team continues using its current process. CHECKS - Use an agreed encrypted transfer channel and restricted temporary storage, with named access and expiry. Real business exports do not belong in a public enquiry form. - Compare transferred files with trusted source SHA-256 checksums where applicable. These fingerprints detect file changes; they do not encrypt data or verify converted business records. - Import in dependency order and record the batch, source IDs, accepted rows and rejected rows. Verify idempotency: re-running the same batch must not create duplicate customers, invoices or payments. Use stable source keys and explicit update rules. - Let staff practise agreed tasks, such as finding a customer, completing an order and recording a payment. Use failures to revise the mapping, import process or training plan. BEFORE SIGN-OFF Every input record is accounted for as imported, rejected or deliberately excluded, and a repeated import does not duplicate transactions. Staff can complete the agreed trial tasks. WHAT YOU RECEIVE The trial import log, rejected-record list, file-integrity results and staff feedback. ---------------------------------------- 4. PROVE THAT RECORDS AND BALANCES AGREE Reconciliation · Referential integrity · UAT Matching the number of rows is only one check. The business must be able to rely on the figures and relationships too. CHECKS - Compare source and destination counts for each record type, period and status. Explain every missing, duplicate, rejected or intentionally excluded record. - Where relevant, compare stock by item, location and unit; unpaid invoices and supplier bills by currency; and payments, credits and opening balances. Agree any permitted rounding differences explicitly. - Test referential integrity: invoices must link to existing customers and the correct payments, with no orphaned records. Check that attachments open. Use file checksums for unchanged files and agreed record-level comparisons for transformed data. - Run user acceptance testing (UAT) with your team: find an old invoice, trace a part-payment, check available stock and produce the agreed report. Record who accepts each business task. BEFORE SIGN-OFF Unexplained balance differences, missing required records or a failed critical task block approval. Any accepted exception names the records, impact and person approving it. WHAT YOU RECEIVE A source-to-destination comparison, exceptions register and your team’s signed-off acceptance results. ---------------------------------------- 5. APPROVE THE SWITCH AND REHEARSE THE FALLBACK Delta synchronisation · Cutover runbook · Rollback Set a clear time when the new system becomes the working record, with someone authorised to stop the move. CHECKS - Agree the switch window, staff instructions and any pause in updates. Plan delta synchronisation for changes since the trial, including new payments, cancellations and deletions. Assess change data capture (CDC) only where the source, permissions and target support it; otherwise use controlled exports and reconciliation. - Repeat the agreed checks on the final records. Name who gives the go-ahead, the decision deadline and the failures that require postponement, such as an unexplained balance or blocked order workflow. - Rehearse how to restore the previous service. Before reverting, preserve and reconcile orders and payments created during the change; routing users to an older database could otherwise lose that work. BEFORE SIGN-OFF The client approves the final comparison and confirms where staff should enter new work. The fallback has an owner, tested steps and a way to account for transactions made after the switch. WHAT YOU RECEIVE A timed cutover checklist, final reconciliation, recorded go-ahead and rollback instructions. ---------------------------------------- 6. SUPPORT THE TEAM AND CLOSE OUT THE MOVE Hypercare · Operational handover · Decommissioning Keep checking the new system through the agreed support period before retiring the old one. CHECKS - Agree the hypercare period: additional support and monitoring immediately after the switch. Review newly entered orders, invoices, payments and stock movements. Log issues, owners and resolutions, with named support contacts, coverage hours and exit criteria. - Hand over staff instructions, account ownership and an export sample. Keep the mapping, migration logs, reconciliation results and acceptance record together for future reference. - Agree how long the old system or archive remains available and when it can be retired. Revoke temporary access and confirm removal of temporary exports under the agreed retention policy. BEFORE SIGN-OFF Your nominated owner accepts the handover, staff know where to get help, and the retention decision is recorded before old records or systems are removed. WHAT YOU RECEIVE The handover pack, support arrangements, outstanding-issue register and access-removal record. ---------------------------------------- PROJECT REVIEW RECORD Project: ____________________ Technical owner: ____________________ Client decision-maker: ____________________ Agreed scope and exceptions: ____________________ Evidence reviewed: ____________________ Open actions, owners and dates: ____________________ Approval and date: ____________________ ---------------------------------------- Contact: contact@ceuscapital.com · +65 8347 2758 Please arrange a restricted transfer channel before sharing confidential records.