Skip to content

01Real-time case study

K2 replacement in days. Your own system in 43 hours.

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.

LiveUpdated 15. 11. 2026 at 8:41
  • Instance in 43 hours
  • K2 data in 1 h 48 min
  • 56 % weekend work
  • Every change tested
Female service technician and colleague inspecting a laboratory centrifuge with a tablet
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
167,831
historical documents from K2 searchable in the new system archive
24 460
service tickets with attachments

02The stopwatch started at signing

Time since contract signing: 15. 10. 2026, 13:06

  1. 01

    T + 0

    Client signed the contract

  2. 02

    T + 43 h

    Saturday 8:08: instance running with the data model from the analysis

  3. 03

    T + 80 h

    Sunday evening: user manual, 302 pages

  4. 04

    T + 13 days

    Companies, contacts, products and orders from K2 in the system

  5. 05

    T + 21 days

    1 848 contracts and first trial inventory migration

  6. 06

    T + 24 days

    Integrations verified live: online stores, email, Czech data box (ISDS)

03Why the relentless pace

Changes deployed within hours. Every single one verified by automated tests.

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.

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.

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.

04Timeline

Every milestone with date and time

Timestamps come from our deployment logs and project records. We update them continuously, sprint by sprint.

Before the contractJune 2025 – August 2026

Analysis: knowing what to build before signing

  1. 10. 6. 202514:30

    First in-person meeting

    Getting to know the company, K2 and where manual work happens today.

  2. 29. 7. 202608:55

    Audit of 320 activities

    Breakdown of materials by department: sales, public tenders, delivery, logistics, service, accounting.

  3. 29. 7. 202609:44

    Analysis complete: 20 chapters, 74 pages

    Target architecture, workflows, data model, K2 migration, permissions, phases and acceptance tests.

  4. 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 online store integration.

  5. 18. 8. 202607:44

    Analysis version 2.0

    Sixteen areas of the client's vision mirrored one-to-one. Every statement traceable to its source.

Contract15. 10. 2026

Signature

  1. 15. 10. 202613:06

    “So it's signed. What do we start with, and how? :)”

    Client's email. From this moment the stopwatch is running.

Sprint 117. – 19. 10. 2026

Instance from analysis in 43 hours

  1. 17. 10. 202608:08Saturday

    Client configuration created

    The instance is built from the analysis, not from a blank template.

  2. 17. 10. 202608:24Saturday

    Data model from analysis

    Order, public tender, batch, installed equipment, service contract, inspection plan.

  3. 17. 10. 202612:39Saturday

    Online store orders flowing into the system

    Connector tested on a store sample with duplicate protection.

  4. 17. 10. 202614:21Saturday

    Document export to ABRA Flexi enabled

    ISDOC to the export folder. 91 changes in the client configuration on day one.

  5. 18. 10. 202621:32Sunday

    User manual: 302 pages

    49 of 49 system walkthroughs green, 289 screenshots. Another 80 changes that day: order margins, loss-making orders, online store exception queue.

  6. 19. 10. 202606: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.

Sprint 222. – 29. 10. 2026

Inputs, credentials and K2 data

  1. 23. 10. 202606:09

    Analysis of 138 client files

    59 MB of materials: accounting, sample documents, recycling fees, freight invoices. Ten key findings written up overnight.

  2. 26. 10. 202613: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.

  3. 27. 10. 2026

    Client handed over credentials

    Network VPN, read-only K2 database, email, e-intranet.

  4. 28. 10. 202608:45

    Connected to K2 via VPN

    Isolated connection with two-factor authentication. We never write anything to K2.

  5. 28. 10. 202610:33

    Live K2 data in Draivix

    Companies, contacts, products and open orders. 1 hour 48 minutes after connecting.

  6. 28. 10. 202610:43

    Archive of closed K2 documents

    Plus open purchase orders. Full history remains searchable in the new system.

  7. 28. 10. 202611: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.

  8. 29. 10. 2026

    Access to ABRA Flexi

    Both companies ready for trial document export to accounting.

Sprint 33. – 8. 11. 2026

Kick-off and live integrations

  1. 4. 11. 202610:00

    Project meeting with the client

    Walking through the system on their own K2 data.

  2. 4. 11. 202612: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.

  3. 5. 11. 202611: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.

  4. 5. 11. 202617:24

    First trial inventory migration

    1 735 items across eight warehouses, discrepancies against K2 listed for reconciliation.

  5. 6. 11. 202600:42at night

    E-intranet migrated

    24 460 service tickets with attachments. Two-factor authentication enabled for everyone that same day.

  6. 8. 11. 202617:23Sunday

    Integrations verified live

    Both online stores, 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.

Sprint 49. – 15. 11. 2026

The client tests on its own data, first live entries in accounting

  1. 9. 11. 202612:50

    Trial migration of open receivables and payables from K2

    A dry run over 562 open documents of both companies (368 issued, 194 received): 476 become invoices with their original number, dates and amount paid so far, 79 have a balance under CZK 1 and 7 credit notes will be entered by hand.

  2. 9. 11. 202616:09

    First live entries in ABRA Flexi for both companies

    With the accounting firm's consent, one issued and one received invoice with its PDF went into the books of each company. At 16:23 the accounting firm confirmed the entries and attachments.

  3. 10. 11. 202613:41

    Disputed serial numbers resolved the same day

    At 10:47 the client's management sent its decision on disputed serial numbers; by 13:41 it was in the system: 48 devices took the customer and warranty from the confirmed card, 18 pairs now have two separate cards and 4 invalid records are not migrated.

  4. 11. 11. 202612:35

    Client logistics completed the stock inputs

    The client filled in the stock cards with serial numbers and the quantity and unit differences. We also agreed that pipettes are stocked without serial numbers and the number from the delivery note goes onto the customer's device card.

  5. 12. 11. 202612:35

    AI assistant in a closed mode over the client's data

    The assistant runs isolated, with no access to HR records or data boxes. Extraction of documents from mail stays off until the data processing agreement is signed.

  6. 13. 11. 202612:34

    Orders since 2023 with K2 texts and addresses

    248 orders since 2023 that are not fully invoiced yet, with header and footer texts, addresses and numbers from the K2 series. Customers carry bank accounts (4,099 at 1,917 companies) and payment terms; K2 attachments now total 120,430.

  7. 13. 11. 202623:59

    The client creates orders on its own: test passed

    The client's tester created an order in the system and confirmed the test passed, sending further suggestions in the same message; we built them the next day.

  8. 14. 11. 202614:54Saturday

    Purchase order test and 15 changes the same day

    The client tested a purchase order on real goods. By the evening we had deployed 15 changes: order numbers per group company, supplier picker with company ID and address without partners ended in K2, warranty on the order line and natural sorting of order numbers.

  9. 15. 11. 202608:41Sunday

    Contract parameters read straight from the attached contract

    The system reads repair response times, warranties and penalties from the attached contract and proposes them as contract parameters for review. Requested on 13. 11., done on Sunday morning.

05In progress · 9. – 20. 11. 2026

Sprint 4: complete data in trial migration

The client is testing the system on its own data. We are finishing the trial stock migration including split packs, tuning the ABRA Flexi export postings with the accounting firm and registering automatic bank downloads. On Monday 16. 11. we close the last decisions on orders and invoices with the client.

Client inputs and credentials delivered21 / 31
Our deliverables completed or ready19 / 32
Integrations working11 / 15
  • ABRA Flexi export postings and number series per the accounting firm
  • Bank API: certificates of both companies uploaded, app registration at the bank pending
  • Open receivables (368) and payables (194) from K2 at cutover
  • Stock after inventory including split packs; contract parameters for client review

06Road to go-live

What remains until 1. 1. 2027

  1. M0done

    8. 11.

    K2 data in the system, management access

  2. M1active

    13. 11.

    All inputs and credentials from the client

  3. M2active

    20. 11.

    Complete data in trial migration

  4. M3active

    27. 11.

    All integrations tested live

  5. M4planned

    30. 11. – 11. 12.

    Full system testing on client data

  6. M5planned

    7. – 18. 12.

    Users and role-based training

  7. M6planned

    18. 12.

    Go-live decision

  8. M7planned

    30. 12. – 1. 1.

    K2 freeze and final cutover migration

  9. M8planned

    1. 1. 2027

    Live production in Draivix

07Status as of 14. 11. 2026

What is already in the system

4 069
companies from K2, shared across both entities
13 442
product stock cards
21 430
customer devices with serial numbers
167 831
documents in the K2 archive
120 430
document attachments from K2
1 972
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 online stores

    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

Four principles that let us deliver in days, not months

01

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.

02

Configuration before custom code

Most needs are configured. We code only what configuration cannot do, and automated tests verify every change.

03

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.

04

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