Multi-entity rollout archive context checklist: three windows before the legacy books go dark

Short answer

Partly, and the answer changes as the rollout advances. Before the rollout is announced, the people who booked and approved old intercompany corrections are all still there. By cutover, the migration scope has decided which detail moves. Once the legacy books are switched off, any approver who was never written down is usually gone for good. This checklist sets out what to confirm in each of those three windows, who owns each item, and what is lost if it is skipped. It uses only dates the company itself has set.

Visual briefFull-size diagram
A vertical countdown with three windows, before announcement, before cutover and before switch-off, where three checklist items tick off in each window before the legacy books are turned off.
Illustrative. Dates come from the company's own contracts and plan; none are assumed.

It supports the guide on which entity owns the data in a multi-entity group. The rollout playbook explains why this history matters; the checklist is the working document.

How to use the checklist

Fill it in with the controller, a line at a time, in the steering meetings you already hold. Every answer is a name, a date, a count or a yes or no. Nothing on it requires opening a journal, memo or email, and nothing on it should be copied out of the company's systems.

Illustrative. The worked entries come from a fictional 330-person dental laboratory group with five entities: four regional labs and a holding company that owns the equipment and employs the finance team.

Window 1: before the rollout is announced to the entities

At this point the legacy finance staff in each entity do not yet know their books are moving. It is the cheapest moment to record who did what.

ConfirmOwnerIf skippedIllustrative entry
Which person approved cross-entity corrections in each legacy ledgerGroup controllerApprover names leave with the peopleTwo regional accountants and the group controller
Where explanations for corrections were keptGroup controllerReasons survive only in inboxesMemo field in two labs, email in three
First year of usable detail in each ledgerEach entity's bookkeeperNobody can say how much history exists2017 for three labs, 2020 for two
Which entity employs the people who made the correctionsHR or controllerWrong entity is asked to authorize laterHolding company

Window 2: before cutover weekend

Migration scope is now fixed or nearly so. The question shifts from who knew to what moves.

ConfirmOwnerIf skippedIllustrative entry
Whether detailed history migrates or only balancesImplementation lead and controllerPre-rollout corrections exist only in the old systemTwo years of detail; earlier years balances only
Whether journal approvals are switched on from day oneControllerNew entries also lack an approverRequired for all intercompany journals
Whether the new account will use System Notes v2NetSuite administratorThe changing user's role, and notes on deleted records, are not keptEnabled
A reference list mapping each legacy ledger to its new subsidiaryControllerOld corrections cannot be tied to the right entityFive rows, one per entity

Why the second and third rows matter: with approvals required, an unapproved journal does not post (Oracle NetSuite), and System Notes v2 records the user's role and keeps information about deleted records, which classic system notes do not (Oracle NetSuite). Both settings decide whether future corrections carry the entity and approver without anyone having to remember.

Window 3: before the legacy books go dark

The old subscriptions or servers have an end date. After it, read-only access may lapse and files may be deleted.

ConfirmOwnerIf skippedIllustrative entry
The date access ends, as stated in the legacy contract or renewal noticeControllerThe deadline is guessed, or missedStated in the renewal notice; not assumed
A complete company-held export of each legacy ledgerIT leadHistory disappears with the subscriptionExported and verified by IT
Reconciliation workbooks retained alongside the exportGroup controllerReasons for corrections are separated from the entriesKept in the finance archive
Who holds credentials for the archive after go-liveIT leadNobody can open the export laterRole recorded, not the credentials
Decision on whether to explore a licensing reviewCEOThe topic drifts without an answerExplore after go-live

If several small-business ledgers are being merged, the page on consolidating multiple QuickBooks companies covers the per-file questions; groups on another mid-market ledger can compare with Sage Intacct data for AI.

Dates only the company can supply

The checklist deliberately has no default deadlines. Every date on it must trace to a document the company holds: a renewal notice, a cutover plan, a decommissioning ticket. If a date cannot be traced, write "unknown" and move on. Inventing urgency to speed a decision would damage the trust the introduction depends on, and SourceX's own review does not run to the rollout's timetable.

Two dates usually matter most: the end of legacy access and the migration scope sign-off. The first decides whether history survives at all; the second decides whether it survives inside NetSuite or only in an export.

What the finished checklist tells you, and what it does not

A completed checklist answers the qualifying question at metadata level: for which years the company can identify the entity and approval behind each adjustment, where those records sit and who owns them. It also names the entity whose CEO would authorize a licensing discussion; where systems are shared across entities, see who owns data in a shared group system and the guide to finding a company's legal entity name.

It does not tell you whether SourceX would select any of it, what the rights review would find, or what any payout or reward would be. Before introducing anyone, check the baseline (50+ full-time employees at peak, contractors excluded; documented operating history; rights to license; an authorized contact). 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. Then sign the Channel Partner Agreement. If the officer wants to proceed, use the meeting agenda to confirm the decision.

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 Window 3 ends with an officer choosing to explore a review, register as a partner, confirm the group against who qualifies and share the terms with that officer.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

What if the company has no switch-off date yet?

Record it as unknown and revisit at the next scope review. The checklist works on dates the company has set; it never assumes one.

Does completing the checklist mean the history is worth licensing?

No. It means the context needed to assess it survives the rollout. Whether any records are selected, and on what terms, is decided only after SourceX reviews the company.

Can the implementer keep a copy of the exported history?

No. The company keeps its own records. The implementer's notes hold counts, dates, owners and yes-or-no answers only.

Sources

  1. refer.sourcex.si/terms
  2. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/articl…
  3. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment