Data that does not fit
Duplicate customers, free-text fields, missing references and years of workarounds in the old system. Migrated as-is, it breaks the new one on day one.
Implementation and deployment
Software Implementation and Go-Live Support in the UK
New systems rarely fail in the code. They fail at go-live — bad data, missed integrations, staff nobody trained. We plan and run the move from the old way of working to the new one, whether we built the system or you bought it.
- Cutover rehearsed before the real thing
- A written rollback plan for every go-live
- Hypercare while your team settles in
Why go-lives go wrong
Go-live problems are usually planning problems.
The software can be finished and tested and the launch can still go badly — because the data, the people and the fallback plan were left until the final fortnight.
What a calm go-live looks like
Good implementations feel almost uneventful on the day, because the hard work happened before it:
- Data cleansed and migrated in rehearsals, with counts that reconcile
- Every integration listed, tested and owned by someone
- A cutover plan timed to the hour, with go/no-go checkpoints
- Staff trained on their own tasks, close to launch
- A rollback route that has actually been tried
Integrations found late
The export to the finance system, the nightly file to a supplier, the spreadsheet someone emails every Monday — undocumented, and discovered after cutover.
Staff who were never shown
One training session weeks before launch, generic manuals and nobody to ask. People drift back to the old system or to workarounds, and adoption stalls.
No way back
The old system was switched off the moment the new one went live, with no rehearsed rollback — so a bad Monday morning becomes a bad month.
What we do
Implementation support, from set-up to hypercare.
For software we build and for platforms you have bought: we configure, connect, migrate and launch — then stay close while your team settles in.
SaaS configuration
Set up the platform you have bought — workflows, roles, permissions, templates and single sign-on — to match how your organisation actually works.
Digital transformation
Integrations
Connect the new system to your finance, CRM, HR and identity platforms — Xero, Sage and the rest — through APIs, webhooks or scheduled files where nothing better exists.
API integration
Data migration and cleansing
Profile, deduplicate and map your old data, run repeatable migration scripts, and reconcile record counts and totals so finance and operations can sign off.
Migrations and upgrades
Cutover planning and rehearsal
An hour-by-hour runbook with owners, go/no-go checkpoints and a timed dry run, so the real cutover is the second or third time the team has done it.
Deployment automation
Training and documentation
Role-based guides, short recorded walkthroughs and train-the-trainer sessions for your champions, written in your terminology rather than the vendor’s.
Discuss this
Hypercare after go-live
A defined period of close support after launch: daily check-ins, a quick triage route for issues, and a planned handover to business-as-usual support.
Ongoing support
How we work
How we take a new system live without drama.
Seven stages, weighted towards preparation: most of the effort goes into data, integrations and rehearsal, so the go-live itself is short and predictable.
- 01
Discovery
We map what the old system does — including the undocumented jobs, exports and spreadsheets around it — and who depends on each part.
Inventory of processes, data and integrations
- 02
Strategy
We choose the cutover approach — single switchover, phased by team or site, or a short parallel run — and agree go/no-go criteria and the rollback trigger.
Cutover strategy and go/no-go criteria
- 03
UX & architecture
Configuration, field mappings and integration designs are agreed with the people who will use them day to day, not just the project sponsor.
Signed-off configuration and data mapping
- 04
Development
Configuration, integrations and migration scripts are built in sprints, with a trial migration of real data early enough to learn from it.
Repeatable migration and tested integrations
- 05
Testing
Full dress rehearsals: migrate, reconcile, run key processes end to end, then practise the rollback. We repeat until the timings and counts are boring.
Rehearsed cutover with reconciled data
- 06
Launch
The cutover runs to the runbook, with checkpoints where the business decides to continue or roll back — and the old system kept read-only as a reference.
Live system and a closed-out cutover log
- 07
Optimisation & support
Hypercare with daily check-ins and quick fixes, then a handover to business-as-usual support with the known-issues list and documentation to match.
A stable system and a clean handover
Technology
What we use to move you across safely.
Most of the craft is process rather than tooling, but the right scripts and environments make each rehearsal repeatable instead of heroic.
Data migration
Python migration scriptsPostgreSQL and MySQLProfiling and deduplicationReconciliation reports
Integration
REST APIs and webhooksScheduled file transfersNode.js integration servicesQueues and retries
Identity and access
Single sign-onRole and permission mappingJoiner, mover and leaver processesAccess reviews
Deployment
AWSDockerGitHub ActionsSeparate staging and production
Training and adoption
Role-based user guidesRecorded walkthroughsTrain-the-trainer sessionsIn-app help text
Cutover control
Hour-by-hour runbooksGo/no-go checkpointsRollback proceduresIssue and decision logs
We implement platforms we have built and third-party products alike. For a vendor’s product, we work alongside their support team rather than around it.
Use cases
Go-lives we help UK teams through.
Typical projects, from swapping out a single system to rolling out a platform across several sites.
Moving to a new accounting platform
Chart of accounts mapped, opening balances migrated and reconciled, and bank feeds, payroll exports and invoicing integrations reconnected before month end.
Replacing spreadsheets with a system
Years of spreadsheet data cleansed into a proper database, with the formulas people relied on turned into rules they can see and trust.
CRM switchover
Contacts deduplicated, history migrated, email and phone integrations reconnected, and pipeline stages rebuilt around how your team actually sells.
Phased rollout by location
One pilot site first, lessons folded back in, then the remaining sites in waves — each with local champions trained before their go-live date.
Moving customers to a rebuilt platform
Existing customers moved from the old version to the new one with accounts, data and saved settings intact, and communications timed to each step.
Go-live with an audit trail
Documented test evidence, sign-offs and a decision log for each checkpoint — the record your auditors, DPO or governance board will want to see afterwards.
Relevant work
Products we have designed and built.
A selection of client projects related to this work. Each case study covers the brief, the approach and the stack.
All case studiesEducation · SaaS
University Management
University management system replacing spreadsheet enrolment and timetabling.
ReactNode.jsPostgreSQLAWS
Read the case studyManufacturing · B2B
Teflon Bone
B2B catalogue, bulk ordering and export platform for a manufacturer.
Next.jsNode.jsStripePostgreSQL
Read the case studyFinance · Analytics
Modernize
Revenue analytics dashboard with multi-source data and automated reporting.
ReactNode.jsPostgreSQLD3.js
Read the case studyWhy Techsleight
What working with us is actually like.
No inflated numbers — just how we run projects, and what you can hold us to.
Product engineering, not ticket-taking
We ask what the software is for before we estimate it — and we will tell you when something should not be built, or should be bought instead.
AI where it earns its place
LLM features, retrieval and automation built with evaluation, guardrails and cost controls, and plain software where that is the better answer.
Full-stack under one roof
Design, frontend, backend, mobile, cloud and QA in one team, so nothing falls between suppliers.
UK-focused delivery
UK business hours, estimates in pounds, and a contract with a UK company. Our engineers are based in the UK and India.
Flexible engagement
A fixed-scope project, dedicated developers or a monthly retainer — and you can move between them as the work changes.
You own everything
Code, IP, cloud accounts and documentation are yours from day one. We sign an NDA before discovery if you need one.
Support after launch
We stay on for fixes, upgrades and new features, or hand over cleanly to your in-house team with the documentation to match.
FAQs
Questions we get asked.
Straight answers on scope, cost, timelines and how we work. If yours is not here, ask us directly.
Do you only implement software you have built?
No. We also implement third-party platforms — configuring them, connecting them to your other systems and migrating your data in. Where the vendor provides its own implementation support, we coordinate with them so responsibilities are clear and nothing falls between the two teams.
What is hypercare?
A defined period straight after go-live when support is at its most intensive: daily check-ins, a direct line to the people who configured the system, and quick fixes for the issues real use uncovers. It ends with a planned handover to normal support once the system is stable.
Should we switch over all at once or in phases?
It depends on how connected your teams and data are. A single cutover is simpler when everyone shares the same data; a phased rollout by team or site reduces risk when groups work independently. Parallel running sounds safe but doubles the workload, so we recommend it only for short periods on critical processes.
How do you make sure migrated data is correct?
Through reconciliation, not hope. In each rehearsal we compare record counts, financial totals and a sample of individual records between the old and new systems, and the people who own that data check the results. Anything that does not match is explained or fixed before the real migration.
What happens if the go-live goes wrong?
We follow the rollback plan agreed in advance. Every cutover has checkpoints where the business decides whether to continue, and a rehearsed route back to the old system if a problem cannot be fixed in time. Keeping the old system available read-only for a period also helps answer questions after launch.
How long does an implementation take?
It depends more on data and integrations than on the software itself. A single system with clean data and a couple of integrations is a contained project; a multi-site rollout with years of legacy data takes longer. After discovery you get a dated plan with the rehearsals and go-live built in.
How do you train staff on a new system?
By role, and close to go-live so it sticks. Each group learns the tasks they will actually do, using realistic data where possible, backed by short guides and recorded walkthroughs. We also train internal champions, so people have someone nearby to ask once we step back.
How do you handle UK GDPR during a data migration?
We move only the personal data the new system needs, use secure transfer and restricted access during the migration, anonymise test copies where possible, and delete working extracts afterwards. We can document the data flows for your DPIA and records of processing; sign-off stays with your DPO.
What does an implementation cost?
We start with a paid discovery, from £2,000, that inventories your processes, data and integrations and produces a cutover plan. The implementation is then quoted at a fixed price with milestone billing, and hypercare is agreed as a defined block of support rather than an open-ended commitment.
Can you rescue an implementation that has stalled?
Yes. We review where it stands — configuration, data quality, open issues and who has decided what — then give you an honest assessment and a revised plan. Often the fix is not technical at all, but a missing decision or nobody owning the data.
Start a project
Planning a go-live?
Tell us what is being replaced, what it connects to and when you need to be live. We will help you see the risks early and plan a cutover your team can rehearse.
What happens next
- 1A senior engineer reads your brief within one working day, and replies with questions or a first view.
- 2A 30-minute call to understand the goal, constraints and what good looks like — no sales script.
- 3A written proposal with scope, milestones, team and a GBP estimate you can take to your board.
Techsleight Labs is a trading name of Krapton IT Consultancy.
Explore