Spreadsheet to fund management system: a controlled migration playbook

There is no universal asset, investor, vehicle, or portfolio-company threshold that makes a spreadsheet unsafe. The decision should follow observable control strain: conflicting versions, manual re-entry, slow close and reporting cycles, missing change history, access that cannot be limited by role, or repeated reconciliation exceptions. Write down the current failure modes and the target outcomes before evaluating software.

Governing documents and accounting policies control. The migration cannot change commitments, allocations, fees, waterfalls, valuation policy, investor rights, or reporting obligations merely because the target system models them differently. Identify the legal entity, controlling document, accounting basis, operational owner, and authoritative source for every data domain before mapping fields.^5,1

Create a field-level map from each source to the target system and every required output. Define names, identifiers, formats, effective dates, currencies, signs, accounting treatment, null handling, and the owner who may approve a transformation. ILPA's current templates provide useful output schemas for quarterly reporting, performance cash flows, capital calls, distributions, and unfunded commitments, but they supplement rather than override fund records and policies.^1,2,3

Take dated, read-only exports before changing source data. Hash or otherwise identify the exact files, record their owners and extraction parameters, and restrict access to the migration team. Perform normalization in controlled working copies so every renamed entity, reformatted date, merged record, corrected sign, or filled field can be traced back to the original value and an approved reason.⁴

A successful import starts with records that already agree. Tie commitments, calls, distributions, unfunded balances, ownership, cash, investments, fees, expenses, and capital accounts to the applicable legal, banking, administrator, and general-ledger records. Resolve or explicitly carry each difference. A target platform should not become the place where unexplained source discrepancies are hidden.^1,2,3

Feature lists and headline prices do not establish operational fit. Test entity support, permissions, segregation of duties, approval states, audit history, document controls, calculation transparency, exportability, integrations, incident handling, backup and recovery, service commitments, and the provider's evidence for security claims. NIST CSF 2.0 offers a useful governance framework without prescribing a single product or certification.⁴

Load a representative subset first. Configure entities, roles, approval rules, accounting mappings, reporting definitions, document folders, notification templates, and integrations under change control. Keep production communications and payment instructions disabled until the configuration has been reviewed. Any workaround should have an owner, risk assessment, compensating control, and retirement plan.⁴

The migration acceptance test should reproduce critical outputs from source evidence through the target system. Test opening balances, transaction history, investor statements, capital call and distribution detail, performance cash flows, permissions, approvals, exports, corrections, and recovery. Compare at both record and aggregate levels. A passed screen walkthrough is not evidence that calculations and controls work.^1,2,3

Choose a live operating cycle that exercises the important records and controls, then produce it from both the existing process and the target system. The appropriate duration depends on vehicle complexity, reporting cadence, data quality, and risk; it is not a fixed number of weeks or quarters. Compare calculations, approvals, delivery files, accounting entries, and exception handling before authorizing cutover.^1,3

Freeze source changes, take final extracts, load approved deltas, rerun reconciliations, activate production roles, and record the cutover decision. Preserve the legacy files as controlled, read-only records according to counsel-approved retention policy; do not delete them simply because the new system is live. Close the migration with a reproducible evidence package and a list of post-cutover monitoring checks.⁴