Equity

The migration atlas compares every value in the old fundamental data with the new data. You can filter it by year, property, and company, and expand each property group to show its properties and period windows. Each row shows whether the values are identical, changed, reduced, lost, or new, and the measured reason for each change. To view the atlas in a separate tab, open the QuantConnect Morningstar Fundamentals Migration Atlas.

The old feeds dated the ratio, growth, per-share, and average properties at the end of the reporting period. The company filed the statement behind these values weeks later. In the new dataset, these properties take the filing date of the statement they come from. Most of their values now arrive later than before, by a median of 63 days.

Backtests and research on the old dataset could read these values before they were public. Live algorithms only receive the data that the vendor delivers each day, so they never received these values early. Strategies that rebalance soon after the end of a fiscal period now wait for the filing before they receive the new values.

The new dataset starts in January 1998, like the old one, and covers more US Equities. A larger dataset changes universe selection, even for companies whose values didn't change. For example, if you select the 500 companies with the largest dollar volume that have fundamental data, the selection now comes from a larger pool. Companies near the cut-off can drop out of your universe. The HasFundamentalDatahas_fundamental_data property works as before and returns trueTrue for more securities.

Morningstar no longer provides some data points, or some period windows of them. LEAN keeps the corresponding members so your algorithms still compile, but the members are obsolete and throw a NotSupportedException when you read them. The exception message names the alternative, if one exists:

DividendCoverageRatio.ThreeMonths was retired by Morningstar in 2026; use DividendCoverageRatio.TwelveMonths.
NormalizedDilutedEPSGrowth was retired by Morningstar in 2026 for all periods; no replacement is available.

Retired members don't break code that loops over the available data. The GetPeriodValuesget_period_values method and the HasValuehas_value property skip retired members, so a loop over the available periods doesn't throw an exception. If the default period window of a property is retired, the property uses a remaining window as its default. As a result, if you read the property without a period, you get the closest available value.

To find the retired members that your algorithm uses, compile your project and run a backtest over a short period. The exception message names the member to replace and its replacement. If a member has no replacement, you must rewrite the logic that uses it.

To measure the effect of the new dataset on your strategy, run the backtest on the old and new datasets and compare the equity curves. To run the backtest on the old dataset, change the LEAN engine branch of your project while the old dataset is still available. If the results differ, find the changes that explain the difference before you change any parameters. The migration atlas and the sections on this page describe each change.

Does the migration change my live algorithms?

Yes. When your live algorithm uses the new dataset, the values differ from the old ones, so the algorithm can select a different universe.

How do I tell whether a specific property changed?

Find the property in the migration atlas. The atlas shows whether each period window of the property is identical, changed, reduced, lost, or new, and the reason for each change.