What You Get
The New System Go-Live Checklist is a three-page PDF for the weeks around a launch, when a new system takes over from a spreadsheet or an older tool. It combines our guides on migrating from spreadsheets to a proper system and managing a software project as a non-technical founder into one list you can work down.
What Is Inside
- Four checks on who owns the code, hosting, domain and paid services, and whether the setup is written down
- A readiness worksheet: your business outcomes, what you have seen working, edge cases and an independent review
- Seven data checks, from the inventory of sheets to a hand-checked test import of 50 to 100 records
- A cutover-day list for record counts, totals and spot checks across the whole file
- An after-launch section with the end date of the parallel run and the day the old file goes read-only
Who This Is For
Owners and operations leads moving a process into a CRM, a client portal, an inventory system or a custom app. It is written for someone who knows the business and the data but not the code. It works whether an agency, a freelancer or your own developer built the system.
How to Use This
Start a few weeks before the planned launch, with the accounts section, because moving a hosting account or repository takes longer than people expect. Fill in the readiness worksheet after each review of working software. Do the data section with whoever knows the spreadsheet best, and keep the mapping document with the project files. The people side of the launch, including training, is covered in how to roll out a new internal system.
Why We Made This
The launches that go badly tend to go badly in the same few ways: a developer holding the only login, data that came across with gaps, or a spreadsheet that stayed editable. This list exists to catch those early. When the data is large, regulated or spread across several systems, our data migration service takes it on.
Get the Checklist
Fill in the short form and the PDF opens straight away. We email you the link too. Everything else we have published is in the resource library.