Migrate from ORCA Financial to Acumatica

Each ORCA fund vehicle maps to an Acumatica Branch (for a single-tenant deployment) or a separate Company within a tenant for multi-fund structures that require isolated ledgers. We preserve the original ORCA fund vehicle identifier as Branch.AlternateID, and we also store the fund’s legal entity name and tax registration ID on the branch record to support regulatory reporting after cutover.

ORCA investor records that are capital-call recipients and distribution recipients map to both a Customer record (for AR/distribution invoices) and a Vendor record (for AP/capital call invoices) in Acumatica. ORCA's investor tier and commitment schedule migrate as user fields on both records.

ORCA commitment amounts, commitment dates, and unfunded commitments are not native Acumatica fields. We create UsrCommitmentAmount, UsrCommitmentDate, and UsrUnfundedCommitment user fields on the Customer DAC, exposing them on the Customer summary screen. These fields are populated during the migration and can be referenced in Generic Inquiries or Automation Schedules for ongoing commitment tracking.

An ORCA capital call event translates to an AP Bill batch in Acumatica, one bill per LP with the fund's GL accounts in the line items. The capital call reference number from ORCA is stored in AP Bill.Remarks and linked to the source fund via branch ID.

ORCA distribution events map to AR Invoice batches in Acumatica. Each LP receives an invoice reflecting their distribution amount per the waterfall. ORCA's distribution type (return of capital, profit distribution, preferred return) maps to a user-defined pick-list on the AR Invoice.

ORCA waterfall results (carry%, preferred return thresholds, LP/hedge splits) have no native Acumatica equivalent. We create a WaterfallResult__c-like custom structure in Acumatica using user fields on the relevant GL account group and a waterfall detail screen via a customization project.

Historical fund transactions—including fee settlements, fund expenses, and deal‑by‑deal gains/losses—migrate as GL batches in Acumatica. Each batch references the fund branch and the relevant subaccount, ensuring that historical balances can be reconciled against ORCA reports at migration close. We also attach migration‑origin notes to each batch for audit traceability.

ORCA portfolio company records map to Customer entities in Acumatica (for receipts and dividend tracking) or to Vendor entities (for cost‑basis and expense reimbursement). ORCA deal‑level custom fields such as sector, vintage year, and acquisition cost are translated into user fields on the appropriate Acumatica record, ensuring all descriptive metadata is retained after cutover.

ORCA deal records map to Acumatica Projects when deal‑level cost tracking, revenue attribution, or waterfall participation must be tracked. The Project.ProjectID is linked back to the corresponding portfolio‑company Customer record, and any waterfall‑related attributes—such as LP‑level carry percentages or preferred‑return thresholds—are stored as user fields on the Project DAC for downstream reporting.

ORCA LP portal user accounts have no direct Acumatica equivalent — Acumatica does not ship an LP-facing portal. We preserve LP portal credentials as a user-field reference and flag this as a functionality that requires a separate Acumatica add-on or third-party portal integration post-migration.

ORCA tracks per‑LP capital account balances, which we represent in Acumatica with a subaccount structure keyed by fund and investor identifiers. The UsrCapitalAccountBalance custom field is added to the subaccount, allowing balance tracking across GL periods. These subaccount balances can be exposed in Generic Inquiries or exported for reconciliation against ORCA’s capital‑account ledger after cut‑over.

Fund‑level expenses recorded in ORCA are migrated as GL journal lines in Acumatica, tagged to the appropriate fund branch and expense subaccount. ORCA’s expense category labels are translated to Acumatica subaccount descriptions, and the migration includes a cross‑validation script that confirms the total expense amount per branch matches the ORCA trial balance before finalizing the cut‑over.

Any ORCA custom properties on fund vehicles, investors, or transactions (e.g., vintage year, investment strategy tag, investor jurisdiction) are translated to Acumatica user fields on the appropriate DAC. Each custom field requires a customization project before migration data can land.

ORCA management fee and carry schedules are fund-level constructs with no Acumatica native equivalent. We store fee percentages, fee bases (committed capital vs. invested capital), and accrual frequencies as user fields on the fund's Branch record and trigger calculations via Acumatica's Automation Schedules.

ORCA’s fund‑level audit trail—including capital call approvals, distribution sign‑offs, and system‑generated alerts—migrates as notes attached to the relevant GL batches in Acumatica. Each note preserves the actor, timestamp, and action description, providing a compliance‑ready audit history that satisfies regulatory review and supports post‑migration reconciliation.