Duplicating a loan in Sonar creates a new loan pre-populated with data from the original. This is useful when you need to run a borrower's scenario under different terms, products, or transaction types without starting from scratch.
Not everything from the source loan carries over — some items are intentionally reset or excluded. Here's a full breakdown of what to expect.
What Carries Over
Nearly all loan data transfers to the duplicated loan, including:
Borrower information — personal details, employment history, addresses, declarations, and consents
Subject property and real estate owned (REO)
Assets, liabilities, and income
Key date fields — the fields are created on the new loan, but their values are cleared. See the note below for exceptions.
Loan conditions — all conditions carry over, including completed and cleared ones, in whatever state they were in on the original loan
Loan notes
Fees (Closing Costs
Documents — non-empty, top-level documents are copied over
Lead data, selected product, and deposit information
Note on Key Dates: Key date fields are created on the new loan but their values are cleared
What Does Not Carry Over
The following items are intentionally excluded from the duplicated loan and will need to be set up fresh:
Loan contacts — loan officers, processors, settlement agents, and other team members will need to be reassigned on the new loan
Milestones and loan attributes — all reset to blank
Audit history and snapshots — the history from the original loan does not carry over
Disclosure packages — no previously sent disclosures are linked to the new loan
Reminder: After duplicating a loan, make sure to reassign the loan team. Loan contacts do not transfer, so the new loan will have no officers or processors assigned until you add them.