# What a long software history tells a partner | SourceX

Canonical: https://refer.sourcex.si/guides/what-a-long-software-history-can-tell-a-referral-partner
Last updated: 2026-11-04

Years in one business system suggest four things: accumulated transactions, configuration that records how the company works, integrations that tie records together and people who understand them. They prove none of the four that matter next: that history survived upgrades, that the records are the company's own, that the CEO wants a licensing conversation, or that SourceX has demand for them. Use a long history to decide whom to ask and what to ask, then let the company confirm.

This guide is for business development leads at channel partners: ERP and CRM resellers, implementers and [managed-service providers](/for/managed-service-providers) who see a client's software from the inside. SourceX's referral site lists IT managed-service providers among those best placed to refer, and says SourceX itself checks each company's history, systems and rights. Your vantage point is valuable and partial at the same time, which is why the questions below matter more than the years on the contract.

## The public clue, and the path to a person

A long software history shows up in three places, and each comes with a different permission.

| Where the clue comes from | Example | What you may do with it |
|---|---|---|
| Public sources | A vendor's published customer story naming the company; job ads asking for experience in a specific system; the vendor's lifecycle page | Use it to decide whom to ask and what to ask |
| Your own service relationship | Ticket history, upgrade projects you ran, user counts you see as reseller or support provider | Use it to decide whether to raise the idea with your contact; disclose none of it without the company's permission |
| The company, in conversation | The CFO tells you order history since 2006 survived two upgrades | Put it in a summary once the CEO approves |

The middle row is the one partners get wrong. Knowing that a client has run the same ERP since 2008 because you have supported it since 2008 is knowledge you hold under a services agreement. It can tell you to ask your account contact a question. It cannot travel to SourceX, or anyone else, as a fact about the company until the company says it.

The relationship path usually runs from your account lead to the CFO, IT director or COO, and from them to the CEO. Only the CEO can authorize a licensing discussion and sign for the company; the others can sponsor the conversation and answer the system questions.

## What years in one system suggest, and what they cannot prove

| A long history suggests | It cannot prove |
|---|---|
| Many years of transactions accumulated in one place | That they were kept: retention settings, purges and fresh-start reimplementations cut history without changing the contract date |
| Fields, codes and workflows that record the company's own way of working | That the records belong to the company rather than to its customers; client-owned material is usually not a fit |
| Integrations that link orders, service, finance and projects | That the CEO wants a licensing conversation |
| Administrators and users who understand what the records mean | That SourceX has demand for them, which it checks in review against current programs |

The left column is why a long history is worth a question. The right column is why it is never worth a claim.

## System maturity discovery questions

Six markers separate a long history from a deep one. Each question goes through your contact, at the metadata level only: no files, screenshots, exports or logins.

| Marker | Discovery question | Who at the company answers | Answer that weakens the signal |
|---|---|---|---|
| Tenure | Since what year has the company run this system, and has it been the same instance throughout? | Finance or IT lead | "We reimplemented in 2019 and started fresh" |
| Carry-forward | At each upgrade or version change, did closed transactions and their history move, or only balances and open items? | Whoever ran the last upgrade | "Only opening balances came across" |
| Configuration | Which fields, codes or workflows did the company add itself, and roughly when? | System administrator | "We use it as it came" (a weaker signal, not a fail) |
| Connections | Which other systems feed it or read from it, and since when? | IT lead | "It stands alone; everything else is spreadsheets" |
| Custody | Who administers it today, and who did before them? | IT lead or CFO | "The one admin who understood it left" |
| Horizon | Is a replacement, upgrade or end-of-support decision on the calendar, and what happens to old history then? | CFO, or the CEO | No answer weakens it; this is a timing question |

Three answers move a company up: history carried through every change, configuration the company built itself, and a named administrator today. Two answers move it down: a fresh start that left the earlier years behind, and records the company holds on behalf of its customers. For CRM-heavy clients, [CRM discovery questions](/resources/crm-discovery-questions) go deeper on sales history, and the [Zoho page](/systems/zoho-crm-export-all-data) shows a four-link depth test for one suite.

## Separating what you observed from what you inferred

Illustrative. Three generic companies with invented facts; none implies an outcome.

| Check | Case 1: public clue only | Case 2: observed, then confirmed | Case 3: long history, no fit |
|---|---|---|---|
| The company | About 600-person food distributor | About 260-person electrical contractor | Surveying firm with 41 full-time employees at peak |
| Where the clue came from | A vendor customer story says it has run the same ERP since 2004 | Your firm has supported its ERP since 2008 | Your firm has supported its system for 22 years |
| Relationship path | Nobody at your firm knows anyone there | Your account lead speaks to the CFO monthly | The founder-CEO is a long-standing client contact |
| What the company confirmed | Nothing | History carried through two upgrades; job-costing codes it built in 2011; an administrator in place; a replacement decision planned for 2027 | Deep, tidy history in one system |
| Decision | No outreach; ask colleagues whether anyone holds a relationship, otherwise drop it | Ask whether the CEO wants an introduction | Record that it fails the size check and the trigger that would change it, peak full-time headcount passing 50 |

Case 1 is the most tempting and the least ready: the clue is public and specific, and there is still nobody who can carry the ask. A cold message to its CEO would be an introduction made without the decision maker's knowledge, which SourceX's screening guidance treats as usually not a fit. Case 3 is the reverse: a warm path and real depth, with a size fact that settles it for now.

## Dated lifecycle events are real timing, not pressure

A long history on a product with a published end date gives the conversation an honest reason to happen now. Two examples from vendors' own pages:

- **Dynamics GP.** Microsoft says technical support, tax updates and product enhancements for Dynamics GP (version 18.x) end on December 31, 2029, with security updates and patches available until April 30, 2031. The [Dynamics GP end-of-life page](/systems/dynamics-gp-end-of-life) covers what that means for GP history.
- **SAP Business Suite 7.** SAP says mainstream maintenance runs through the end of 2027, followed by optional extended maintenance through the end of 2030, and in October 2026 said those dates have not changed. The [S/4HANA transition checklist](/resources/s4hana-transition-archive-context-checklist) lists the archive questions for that move.

A migration is when a company decides how much history to carry forward, archive or leave behind. Asking the carry-forward and horizon questions before that decision helps the client whether or not it ever licenses anything; [legacy ERP data archiving](/guides/legacy-erp-data-archiving) covers the archive side. A renewal date or a quarter-end is not this kind of event, and nothing about an end-of-support date creates a deadline for licensing.

## From a strong signal to a permitted introduction

When your contact's answers keep the signal strong, ask them whether the CEO would welcome an introduction, and say that you would be paid if it led to a license. Then check the fit facts the company has confirmed: at least 50 full-time employees at its peak, not counting contractors; an operating history it can document; rights to license; and location. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Before anything is submitted:

1. **Earlier contact.** Ask whether the company has ever applied to, corresponded with or held an account with SourceX. Any earlier lead, account or email correspondence makes it a duplicate, and duplicates are not credited.
2. **Your agreement.** Sign the SourceX Channel Partner Agreement and hold an approved partner account before you submit any introduction.
3. **The application.** The company applies itself, and credit waits for that verified application: it then goes to a single partner per company, the one whose valid introduction came first within the 90-day attribution window, provided the company was new to SourceX.

## Where a long software history misleads

- **The system survived; the records may not have.** A contract renewed for fifteen years says nothing about purges or reimplementations.
- **Customer stories are marketing.** A vendor's published story dates a relationship; it does not describe what the company kept.
- **Your view is partial.** A reseller sees licenses and tickets, not the company's archive policy or its customer contracts.
- **Long history is not maturity of rights.** Who created the records and what customer contracts allow are decided in SourceX's rights review, with counsel.
- **Programs change.** SourceX applies the criteria of each program, and a company that does not fit one may fit another later. Date every decision. No figures on how software tenure relates to acceptance have been published; to test it, log tenure and carry-forward answers for each company you introduce and compare them with what review found.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When a client's long history holds up under the six questions and its CEO wants the conversation, [register for a partner link](/register), check the confirmed facts against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the company applies. More partner methods for [ERP consultants](/for/erp-consultants) and others are in the [guides library](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/
- https://learn.microsoft.com/en-us/dynamics-gp/terms/lifecycle
- https://news.sap.com/2026/10/beyond-2030-sap-business-suite-7-sap-netweaver-customers-third-party-databases-java/
