01Real-time case study
Replacing K2 in days. Not months.
A distributor of laboratory and pharmaceutical equipment with two companies in its group is leaving K2 on 1. 1. 2027. Its new system was running 43 hours after signing the contract, and K2 data was in it 1 hour 48 minutes after connecting. We move fast because the deadline does not move: we work through weekends, and every change passes automated tests before the client ever sees it.
- Instance in 43 hours
- K2 data in 1 h 48 min
- 56 % weekend work
- Every change tested
- Client
- Two companies in one instance: laboratory and pharmaceutical equipment, service, public tenders
- Replacing
- K2 and e-intranet (HelpDesk); accounting stays in ABRA Flexi
- Go-live
- 1. 1. 2027
- 43 h
- from contract signing to a running instance
- 1 h 48 min
- from connecting to K2 to live data
- 186
- changes deployed on weekends
- 24 460
- service tickets with attachments
02The stopwatch started at signing
Time since contract signing: 15. 10. 2026, 13:06
T + 0
Client signed the contract
T + 43 h
Saturday 8:08: instance running with the data model from the analysis
T + 80 h
Sunday evening: user manual, 302 pages
T + 13 days
Companies, contacts, products and orders from K2 in the system
T + 21 days
1 848 contracts and first trial inventory migration
T + 24 days
Integrations verified live: e-shops, email, Czech data box (ISDS)
03Why the relentless pace
The 1. 1. 2027 deadline does not move. We do not stop either.
56 %
Weekends included
186 of 334 changes to the client configuration were built on Saturday and Sunday. The contract was signed on Thursday; the first instance was up on Saturday at 8:08.
79
While others sleep
That many changes shipped between 22:00 and 6:00. We migrated the e-intranet with 24 460 tickets on Friday at 00:42, and the analysis of 138 client files was ready at 6:09.
49 / 49
Fast, yet fully tested
Every change passes automated pipeline tests or it does not deploy. We ran 49 browser scenarios across the entire system, all green, generating 289 screenshots for the manual.
2 h
Feedback today, fix today
The 4. 11. project meeting started at 10:00 and its feedback was deployed at 12:52. The client tests on their own data and reports issues straight from the system.
04Timeline
Every milestone with date and time
Timestamps come from our deployment logs and project records. We update them continuously, sprint by sprint.
Analysis: knowing what to build before signing
June 2025 – August 202610. 6. 2025
14:30
First in-person meeting
Getting to know the company, K2 and where manual work happens today.
29. 7. 2026
08:55
Audit of 320 activities
Breakdown of materials by department: sales, public tenders, delivery, logistics, service, accounting.
29. 7. 2026
09:44
Analysis complete: 20 chapters, 74 pages
Target architecture, workflows, data model, K2 migration, permissions, phases and acceptance tests.
12. 8. 2026
Recorded workshop with management
Decided: K2 ends on 1. 1. 2027, 1:1 migration of all data, accounting via ABRA Flexi, e-intranet replaced, two-way e-shop integration.
18. 8. 2026
07:44
Analysis version 2.0
Sixteen areas of the client's vision mirrored one-to-one. Every statement traceable to its source.
Signature
15. 10. 202615. 10. 2026
13:06
“So it's signed. What do we start with, and how? :)”
Client's email. From this moment the stopwatch is running.
Instance from analysis in 43 hours
17. – 19. 10. 202617. 10. 2026
08:08
SaturdayClient configuration created
The instance is built from the analysis, not from a blank template.
17. 10. 2026
08:24
SaturdayData model from analysis
Order, public tender, batch, installed equipment, service contract, inspection plan.
17. 10. 2026
12:39
SaturdayE-shop orders flowing into the system
Connector tested on a store sample with duplicate protection.
17. 10. 2026
14:21
SaturdayDocument export to ABRA Flexi enabled
ISDOC to the export folder. 91 changes in the client configuration on day one.
18. 10. 2026
21:32
SundayUser manual: 302 pages
49 of 49 system walkthroughs green, 289 screenshots. Another 80 changes that day: order margins, loss-making orders, e-shop exception queue.
19. 10. 2026
06:50
Module guides and project status
The client receives role-based manuals and an overview of what is done and what is waiting for inputs.
Inputs, credentials and K2 data
22. – 29. 10. 202623. 10. 2026
06:09
Analysis of 138 client files
59 MB of materials: accounting, sample documents, recycling fees, freight invoices. Ten key findings written up overnight.
26. 10. 2026
13:54
50 changes in a single day
Number series matching K2 (payments matched by payment reference), bank accounts, warranty delivery note, handover and decontamination protocol.
27. 10. 2026
Client handed over credentials
Network VPN, read-only K2 database, email, e-intranet.
28. 10. 2026
08:45
Connected to K2 via VPN
Isolated connection with two-factor authentication. We never write anything to K2.
28. 10. 2026
10:33
Live K2 data in Draivix
Companies, contacts, products and open orders. 1 hour 48 minutes after connecting.
28. 10. 2026
10:43
Archive of closed K2 documents
Plus open purchase orders. Full history remains searchable in the new system.
28. 10. 2026
11:43
K2 document attachments
Files are read in read-only mode and linked to documents. Today there are 96 448 of them in the system.
29. 10. 2026
Access to ABRA Flexi
Both companies ready for trial document export to accounting.
Kick-off and live integrations
3. – 8. 11. 20264. 11. 2026
10:00
Project meeting with the client
Walking through the system on their own K2 data.
4. 11. 2026
12:52
Meeting feedback deployed
Under two hours after the meeting ended. At 20:27 that evening, a company switcher: everyone works for one company of the group or the other.
5. 11. 2026
11:28
Commissions, payment approvals, contracts
42 changes in a day: flat and tiered quarterly commissions, payment approvals under client rules, 1 848 K2 contracts matched by number.
5. 11. 2026
17:24
First trial inventory migration
1 735 items across eight warehouses, discrepancies against K2 listed for reconciliation.
6. 11. 2026
00:42
at nightE-intranet migrated
24 460 service tickets with attachments. Two-factor authentication enabled for everyone that same day.
8. 11. 2026
17:23
SundayIntegrations verified live
Both e-shops, reading and sending email from the client's domain, Czech data box (ISDS) (91 messages), K2 archive directly on the customer and device cards. Go-live plan sent.
05In progress · 9. – 20. 11. 2026
Sprint 4: complete data in trial migration
Finalizing client inputs, live test of ABRA Flexi export for both companies, automated bank payment imports, and open receivables and payables from K2.
- Accounting firm sign-off and live export test to ABRA Flexi
- Bank API: hourly transactions
- Open receivables (353) and payables (114) from K2
- Disputed serial numbers and stock discrepancies with client logistics
06Road to go-live
What remains until 1. 1. 2027
- M0done
8. 11.
K2 data in the system, management access
- M1active
13. 11.
All inputs and credentials from the client
- M2active
20. 11.
Complete data in trial migration
- M3active
27. 11.
All integrations tested live
- M4planned
30. 11. – 11. 12.
Full system testing on client data
- M5planned
7. – 18. 12.
Users and role-based training
- M6planned
18. 12.
Go-live decision
- M7planned
30. 12. – 1. 1.
K2 freeze and final cutover migration
- M8planned
1. 1. 2027
Live production in Draivix
07Status as of 8. 11. 2026
What is already in the system
- 4 069
- companies from K2, shared across both entities
- 13 441
- product stock cards
- 21 412
- customer devices with serial numbers
- 167 804
- documents in the K2 archive
- 96 448
- document attachments from K2
- 1 848
- contracts matched to orders
- 1 410
- public tenders
- 30
- users ready for activation
What the system connects to
- K2 · read-only via VPN
- ABRA Flexi · access ready, awaiting live test
- Bank · GPC statements working
- Client email · reading and sending
- Two e-shops · orders in, descriptions out
- Czech data box (ISDS) · both companies
- e-intranet · migrated
- Register of Contracts · pre-invoicing check
- ARES and Czech National Bank rates · working
08Why so fast
Speed is not haste. It is a method.
Analysis before the contract
The day after signing we do not start from scratch: the instance is built directly from the analysis chapters the client already read and approved.
Configuration before custom code
Most needs are configured. We code only what configuration cannot do, and automated tests verify every change.
Legacy system read-only
We repeatedly read data from K2 and never write back to it. The client keeps working in K2 right up to cutover day.
Testing on client data
The client does not test on dummy data, but on their own companies, orders and devices. Feedback is sent straight from the system.
09Frequently asked questions
What companies leaving K2 ask
How long does migrating data from K2 take?
For this client, the first live data (companies, contacts, products and open orders) was in the system 1 hour 48 minutes after connecting to K2. We repeat the migration up until cutover day, when the final delta migration runs.
Do we have to stop working in K2 during the transition?
No. K2 is accessed read-only and the company continues working in it until cutover day. Only then is K2 frozen and kept as an archive.
Will history and attachments be transferred too?
Yes. For this client, the system holds an archive of 167 804 K2 documents, 96 448 attachments and 24 460 service tickets from the e-intranet, searchable directly from the customer and device cards.
Do we have to change our accounting software?
No. The client keeps accounting in ABRA Flexi and the system hands over documents to it. Regular export is enabled only after a successful test on sample documents.
Let’s start together
Want to leave K2 just as fast?
We will show you what the analysis and the first days after signing would look like at your company.
Book a consultation