How to Run Rollover to a New Tax Year Instance (Checklist + Validation Steps)
Step-by-step rollover workflow and validation checklist for setting up a new tax-year Instance.
Summary
This article provides a step-by-step workflow for running rollover from a prior-year Instance into a new tax-year Instance and validating that rollover completed successfully.
Start here for rollover expectations:
For the authoritative list of what should carry forward (and what never does), including optional rollover items and Group Management implications, see K1 Aggregator Rollover: What Carries Forward, What Doesn’t, and How to Configure It.
When to use this article
Use this guide when you need to:
-
run rollover into a new tax-year Instance (single instance or bulk rollover),
-
confirm that rollover completed successfully,
-
validate that expected settings and investment reference data carried forward,
-
complete post-rollover access steps (including Group Management, if enabled).
Before you run rollover (required checklist)
Complete these steps in the prior-year Instance before rollover is initiated:
✅ Confirm optional rollover items are configured (if your workflow requires them)
Examples include: Return ID, investment comments/notes, final K-1 flags, estimate fields.
See: K1 Aggregator Rollover Settings (Optional Items + Where to Configure Them).
✅ Confirm the prior-year Instance is ready
-
Investment list is accurate and complete
-
Tags and ownership data are up to date
-
Basis tracking and activities are configured as expected
✅ Confirm the new-year Instance exists
Rollover carries data into a new tax-year Instance. Verify you’re rolling into the correct year.
✅ If your tenant uses Group Management
Plan to assign the new-year Instance to groups after rollover so users can access it. (Group assignments do not carry forward automatically.)
Important: What rollover does not copy
Rollover does not carry forward tax-year work product such as:
-
uploaded K-1 PDFs or source documents
-
extracted K-1 values / line items
-
annotated PDFs
-
exports or report outputs
For the full list of what does carry forward, see the carry-forward matrix in the pillar article:
K1 Aggregator Rollover: What Carries Forward, What Doesn’t, and How to Configure It.
Step-by-step: Run rollover
Note: The exact menu location may vary depending on how your tenant is configured, but the rollover flow follows the same overall sequence.
Step 1: Navigate to rollover
Go to the location in K1 Aggregator where rollover is initiated (often on the Instance dashboard, Admin setup area, or Rollover tool entry point).
Step 2: Select the prior-year source Instance
Choose the source Instance you want to roll forward from (e.g., 2025 → 2026).
Step 3: Select the new-year destination Instance
Choose the tax-year Instance you want to roll into.
Step 4: Select rollover mode (if applicable)
Depending on your tenant, you may have options such as:
-
Rollover selected Instances
-
Rollover all Instances
-
Bulk rollover (if enabled)
Step 5: Confirm and run rollover
Review the selected source/destination and proceed with rollover.
Post-rollover validation (what to check immediately)
After rollover completes, validate the new-year Instance using the checks below.
✅ Instance-level checks
Confirm:
-
The correct prior-year source Instance was used
-
Core Instance settings appear as expected
-
Return ID appears if it was configured as an optional rollover item
✅ Investment-level checks
Confirm:
-
Investment list exists in the new-year Instance
-
Investment reference data carried forward correctly (name, ownership, tags)
-
Basis tracking configuration and activities are present where expected
-
Optional items appear only if configured (notes/comments, final K-1 flag, estimate column)
✅ Portfolio / foreign forms (if applicable)
Confirm:
-
State loss carryforward data appears as expected
-
Transferee pool / transfers appear if used in the prior-year Instance
Group Management (post-rollover access step)
If Group Management is enabled in your tenant, the new-year Instance will not automatically inherit group-to-instance assignments.
After rollover:
-
Open Tenant Group Management
-
Assign the new-year Instance to the appropriate group(s)
-
Confirm the correct users are included in those groups
-
Confirm any required 7216 consent settings (if offshore access is needed)
If users cannot access the new-year Instance, this is the first place to check.
Common issues (and what to do)
Issue: The new-year Instance is missing investments
Check:
-
You rolled over from the correct prior-year Instance
-
The prior-year Instance investment list was complete
-
Rollover completed successfully
Next step:
Compare expected outcomes using the carry-forward matrix in the pillar article:
K1 Aggregator Rollover: What Carries Forward, What Doesn’t, and How to Configure It.
Issue: Optional items didn’t carry forward (Return ID, notes, comments, estimates)
Most common cause: the optional item was not configured or saved in the prior-year Instance before rollover ran.
Check:
-
Optional items were configured in the prior-year Instance (not new-year)
-
Changes were saved before rollover started
See: K1 Aggregator Rollover Settings (Optional Items + Where to Configure Them).
Issue: Users can’t access the new-year Instance
If Group Management is enabled:
-
the new-year Instance must be assigned to group(s)
-
users must be in those groups
✅ Fix: Assign the instance and confirm user membership in Tenant Group Management.
Issue: Data appears duplicated after rollover
This can occur if rollover is run multiple times or if the same target Instance receives rollover more than once.
Check:
-
whether rollover was run repeatedly for the same year/Instance
-
whether tags or notes were duplicated as part of the optional settings behavior
If duplicates appear, document what duplicated and contact support for cleanup guidance.