FP&A software implementation: how many years of historical data to load

How many years of history should you load into FP&A software?

Load enough actuals to cover the planning cycles the model has to explain: for most mid-sized companies that is three full fiscal years plus the current year to date, and five if the business is seasonal or recently reorganized. Load more only when someone will use it. The decision matters beyond the software, because it forces a client to say how far back its finance records really go and where the older ones live.

This how-to is for fractional and outsourced CFOs running an FP&A rollout for a client. It covers scoping the history, choosing source systems, mapping the chart of accounts, and what to do about older archived systems. It also shows how the same exercise reveals whether a client has the depth of records that could make it a candidate for a SourceX licensing introduction.

Prerequisites before you scope history

• A signed statement of work for the implementation, with a named client owner.
• Read access to the general ledger, sub-ledgers and CRM through the client's own admin.
• A current chart of accounts and a list of past changes to it.
• A list of every system that held finance or sales data in the period, including retired ones.
• A decision on whether the model must reconcile to audited or reviewed statements.

Steps to decide the history window

1. List the questions the model must answer. Forecast accuracy by month, seasonality, cohort revenue, headcount planning. Each question implies a minimum number of periods.
2. Count the cycles. Seasonality usually needs several full cycles to separate pattern from noise. A reorganization or acquisition resets the comparable period.
3. Map each year to a source system. Mark the year ranges for the ERP or accounting system, payroll, CRM, billing and expense tools. Note every migration date.
4. Identify breaks. Chart of accounts changes, entity mergers and currency changes need mapping tables or the older years will not compare.
5. Decide what to load and what to keep. Load what the model uses. Keep the rest in its source or an export. Do not decide to purge anything at this stage.
6. Document the owner of each export. Someone at the client must be able to run it again later.

What is the loading trade-off?

The load window is a planning decision. The records themselves are a separate asset, so older years that you do not load should not be treated as disposable.

Which source systems to connect first

Connect the systems the first forecast depends on: general ledger, billing or revenue, payroll or headcount, and CRM for pipeline-driven revenue. Add expense and procurement tools later. The sales forecast guide shows how CRM history feeds the revenue line, and the customer profitability guide shows how ERP, CRM and support data join.

Common mistakes

What does the history decision tell you about the client's records?

By the end of scoping you know how many systems fed finance and sales, how many years each covers, and whether older systems still exist in archive. Strong companies often have records across 10-15+ systems and 5-10+ years, with archived systems still available. That profile is what a licensing fit check looks for.

Do not ask for access to records for this purpose. Note the system list and year ranges you already have, and answer the baseline: the company had 50+ full-time employees at peak (contractors excluded), has several years of documented operations, owns the records, and has an authorized sponsor (owner, CEO, CFO or authorized representative). The company fit checker gives a preliminary, non-binding screen. See also who qualifies.

Illustrative scenario

Illustrative, fictional: a 180-person services firm moves from one accounting system to another. During scoping, the fractional CFO maps nine years of ledger history, three CRM instances and a retired timesheet tool. She recommends loading four years into the planning tool and keeping the rest as read-only exports. After the project, she asks the owner whether he would like an introduction to a company that handles licensing of operational records. He says yes, and the firm applies through her referral link.

How do you raise the introduction?

Wait until the implementation is stable and the owner is relaxed about the project. Ask permission first.

If the owner agrees, share your referral link, or submit basic company details through the referral form. The company works directly with SourceX on the inventory and terms. Partners never export, upload or describe confidential records. For context on how legacy systems are treated during migrations, see switching to an AI-native ERP, and check who can sign a data license before the owner agrees to anything.

How do rewards work?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward is payable only after the buyer pays and SourceX receives its fee; no reward is guaranteed, and it is never deducted from what the company receives. Check your engagement letter, any professional rules that apply to you, and the program terms. The fractional CFO overview covers the role in more detail.

Next step

At the next FP&A scoping call, write down every system and year range as part of the history decision. If the picture looks deep and the owner is open, register as a partner and introduce the company.