The IBM TRIRIGA® migration
A migration moves your errors at speed, and gives them a fresh timestamp
Systems migrate. Data does not validate itself. If a rent was abstracted wrong in 2019, it arrives in the new system on day one — and now it carries the authority of a freshly loaded record.
The dates every IBM TRIRIGA® customer is working to
All versions and releases of IBM TRIRIGA® software and the IBM TRIRIGA Application Suite.
New software orders have already ended, which shortens the real runway considerably.
For scoping, data preparation, cutover and a parallel reporting period on a portfolio of any size.
Dates per IBM's published support lifecycle notice. Confirm against IBM's own page before relying on them for planning.
Why lease data is the part that fails quietly
- Mapping is not checking
- A migration proves that a value moved from one field to another. It proves nothing whatsoever about whether the value was ever right.
- The abstractor is gone
- The person who entered the original record has moved on, and in most systems nothing records which clause each value came from or who decided the ambiguous ones. There is no trail to re-walk and no way to sample the work.
- The consequence lands later
- Lease data drives the ASC 842, GASB 87 or SFFAS 54 ledger. A wrong commencement date moves every payment in the schedule and changes the term used to discount the liability. It does not announce itself at cutover; it announces itself when an auditor samples it.
- Nobody owns it
- The integrator owns the platform. The client owns the accounting. The lease documents themselves sit between the two, and on most projects the documents are the only artefact nobody is contracted to read.
THE WINDOW ARGUMENT
A migration is the one moment an organisation can justify re-reading its leases: budget approved, attention already on the portfolio, and a date in the calendar. After cutover that window closes for a decade.
How we fit a migration programme
Abstract from source
We work from the lease documents, not from an export of the old system, and deliver a field set with a citation for every value. What loads into the new platform has been read, not copied.
Assure what already exists
A second read of records your team has already abstracted, scoped to exceptions: we report only what disagrees with the document, and why.
Evidence for the audit
The citation file and exception report are built to be handed to an auditor. Pick any delivered value, open the lease, check it.
Send three leases from the portfolio you are migrating
No charge, no commitment. You will know within a week whether the data you are about to move is worth re-reading.