Inventory files and versions
Collect lists of grant, finance, supplier, employee, and inventory files and identify the owner of each file and the reference version. Keep a read-only original before cleaning.
Migrating to TenXshift
From Excel to connected work.
With a plan you can verify.
A suggested migration plan reviewed with your team before execution. Bulk-import tools are available; field, history, attachment, and integration scope needs technical matching.
Turn tables into records
Make every row a record and every column a field; remove merges, multi-row headers, and total rows from the import copy. Clarify what formulas represent, then keep the required value without losing meaning.
Unify references and formats
Choose stable identifiers for grant, supplier, employee, and budget line. Standardise date, currency, and units; preserve leading zeros in identifiers; and do not use name alone to link data.
Clean and review
Review duplicates, missing fields, missing references, and implausible values. Do not delete a record merely because names look alike; ask the data owner for a decision.
Map the template and trial a sample
Review the actual import fields in TenXshift and export the agreed layout. Test reference data first, then the transactions that depend on it, and verify Arabic, encoding, and formats.
Reconcile results and train the team
Compare record counts, balance totals, and grant lines, then try search and a full process cycle with the relevant staff privileges. Log errors and correct them before full cutover.
Adopt one source of truth after go-live
Set a cut-over date and update owner, and move final changes after review. Keep source files as a read-only archive, and do not have the team record the same transactions in two parallel files.
When do we consider migration successful?
Go-live needs approval from data owners and departments — finishing an upload without an error message is not enough.
Data matches
Counts, balances, commitments, and relationships are reviewed against an agreed acceptance list, with differences handled.
Processes are runnable
A sample grant, purchase request, approval, and spend are reviewed through to reporting, with team roles tested.
Rollback plan is clear
The source of truth is retained, freeze boundaries are known, and the rollback decision-maker and handling of new transactions are predefined.
There is no automatic migration tool here, and no guarantee that all Excel data will transfer. Duration, cost, and scope are set after a sample review and field mapping.