How to Migrate Mid-Life Leases into NetSuite
Your team has been calculating lease amortization in Excel and posting journal entries by hand.
Sarah Jenkins, CPAPrincipal Finance Automation Specialist
On this page
Your team has been calculating lease amortization in Excel and posting journal entries by hand. Now you want to move that active portfolio into NetSuite's native lease accounting without restating the entire schedule from commencement. This is the most common ASC 842 migration scenario, and it has a specific set of requirements that catch first-time migrators off guard.
The core challenge: NetSuite expects lease records to start at the original commencement date, but your "mid-life" portfolio already has 18, 30, or 48 months of amortization in the books. You need the opening NetSuite balances to match your Excel subledger on day one, then let NetSuite run from there. Getting comfortable with how the application organizes lease data starts with the standard NetSuite UI navigation so you know where to find each setting referenced below.
What NetSuite Treats as a "Mid-Life" Lease
A mid-life lease is any active agreement where the commencement date is in the past relative to your go-live date. NetSuite does not have a checkbox labeled "mid-life." Instead, it asks for the original commencement date, total lease term, and payment history so it can reconstruct the present value as of the migration date.
Three data points are non-negotiable for every lease you migrate:
- Original commencement date (not the go-live date)
- Discount rate (IBR) formally documented, not estimated
- Amortization history through the migration cutover date
From an audit perspective, missing any of these creates a control gap your auditors will flag within the first walkthrough.
Data Quality Comes Before Migration
Before you touch the import, audit the Excel file. This is where teams lose hours during cutover. The three most common data quality issues are:
- Missing commencement dates (frequently the case for leases assumed through acquisition)
- Inconsistent payment schedules (some monthly, some quarterly, some with step-ups)
- IBRs that were never formally documented or were estimated in a single cell
For leases without a documented IBR, obtain one from your treasury team or lender before migration. A 0.5% variance in the IBR compounds materially over a 10-year term and can shift your lease liability by thousands of dollars. The goal is a clean subledger before NetSuite takes over so the tie-out is defensible.
Configuration Steps in NetSuite
Enable the Lease Accounting feature at Setup > Company > Enable Features, then open the Accounting subtab and locate the Fixed Asset Management section. Confirm that Advanced Accounting is also enabled, since lease amortization depends on it. Without these two features checked, the lease functionality will not appear in your menus.
Next, define your lease types. Common categories include operating versus finance leases, and within each, real estate versus equipment classifications. Configure these in Lists > Accounting, where account-level classifications are maintained per the NetSuite Account Types guide.
| Classification | Use Case |
|---|---|
| Operating - Real Estate | Office and warehouse space |
| Operating - Equipment | Office equipment, vehicles |
| Finance - Real Estate | Owned property arrangements |
| Finance - Equipment | Equipment with bargain purchase option |
Importing Mid-Life Lease Details
Open the asset record associated with the lease from the Fixed Assets menu. When editing the record, populate the lease-specific fields on the relevant subtab:
- Enter the original lease commencement date in the Lease Start Date field
- Enter the lease end date and total term
- Enter the discount rate in the Lease Interest Rate field
- Review the calculated present value
NetSuite will compute the right-of-use (ROU) asset and lease liability based on the discount rate applied to remaining cash flows. Validate that the calculated liability matches your Excel subledger within a $100 tolerance before posting. The control here is a documented tie-out at the cutover date.
Posting the Opening Balance Journal Entry
After the asset record is migrated, post a single opening balance journal entry at the migration date. The entry records:
- Debit: Right-of-Use Asset (by lease type)
- Credit: Lease Liability (current and long-term split)
The current portion is the principal due within 12 months of the migration date. The long-term portion is the remainder. This entry must post to the first open period of the new fiscal year or the period you designate as the cutover period. From an audit perspective, a single dated opening entry is easier to trace than multiple period corrections.
Best Practices for the Migration Window
Close the books in the period immediately before migration. This locks the historical amortization and prevents accidental changes to your opening balances. Then post the migration entries on the first day of the new period.
Run a trial balance reconciliation comparing the new NetSuite lease liability to your Excel subledger. Any variance over your materiality threshold needs investigation before you begin using NetSuite for ongoing amortization. A clean, reconciled, and audit-ready migration requires every assumption to be defensible, and this tie-out is the document your auditors will request.
Configure approval workflows at Setup > Workflow > Workflows. Require controller approval on any lease record modification during the first 90 days post-migration. This prevents accidental edits that would break the tie-out and gives you time to validate NetSuite's automated entries against your Excel schedule.
Common Pitfalls to Avoid
Do not use the go-live date as the lease commencement date. NetSuite will recalculate the schedule from that date and your accumulated amortization will be wrong.
Do not skip the historical cost and accumulated amortization fields on the asset record. Without them, the asset will show a net book value of zero and your ROU asset will be misstated.
Do not migrate leases with undocumented IBRs. Every assumption must be defensible in front of an auditor, and a back-of-the-envelope rate is not.
What to Verify Before Sign-Off
Before declaring the migration complete, confirm three things. First, the lease liability subledger in NetSuite ties to the Excel subledger at the cutover date. Second, the first automated amortization entry posts correctly in the period following migration. Third, your financial statement package reflects the new lease balances and the prior period comparatives are unchanged.
Once these three checks pass, NetSuite owns the schedule from the cutover date forward and your team can stop maintaining the parallel Excel subledger. For controller dashboards that surface the new lease balances alongside other close metrics, the NetSuite Dashboards portlet is the standard place to assemble the post-migration view.
