Nov 30IWB Classic
Our team moves your data to the new IWB
The new IWB is separate, new software, not a version of IWB Classic. We start with a trial run that writes no records, then complete the live migration and measure the result in a handover report.
Nov 30, 2026
last day of IWB Classic technical support
25
module migrators
0.1%
amount variance threshold in reconciliation
01
Timeline
The timeline follows the October 14, 2026 announcement. Your current contract remains valid until its end date.
- Sep 2026
IWB Classic sales stopped
New IWB Classic licenses are no longer sold.
- Oct 14, 2026
The new IWB was released
Released as separate, new software.
- Oct 15, 2026
No new maintenance contracts
Existing maintenance contracts aren't renewed. Contracts already in force remain valid until their end date.
- Nov 30, 2026
IWB Classic technical support endsLast day
After this date, IWB Classic gets no technical support, bug fixes, or security patches. It also won't be updated for regulatory changes such as e-Invoice and e-Ledger rules, or for operating system and database updates. We recommend planning your migration before this date.
02
How the migration works
Our team runs the migration with the migration tool built into IWB. Every step is recorded and can be run again if needed.
- 01
Source connection
We read your IWB Classic data from the existing database with read-only access, or from a copy of the database.
- 02
Compatibility check
Any parts of the old database that the migration needs but can't find are listed in advance. If a required part is missing, the live migration doesn't start.
- 03
Trial run
We preview the result without writing any records, so it's clear up front which records will be created and which warnings will come up.
- 04
Live migration
Records move in the order they depend on each other. When we run the migration again, only changed records are processed.
- 05
Handover report
The source and the new system are compared by record count and amount. The result is marked clean, with warnings, incomplete, or not measured.
03
What moves over and what gets set up again
Everything that doesn't move over is listed by name in the migration report. The original form of every record read from the old system is also kept.
Moves over
- Contacts: addresses, contact persons, bank accounts, and e-Invoice aliases
- Product records, units and unit conversions, the category tree, and barcodes
- Sales invoices and quotes, plus sales orders from projects
- Cash and bank transactions, receipt and payment vouchers, purchase invoices, and the check and promissory note portfolio
- Chart of accounts, fiscal periods, and the general journal
- Stock movement ledger and warehouses, plus bills of materials and production orders
- Purchase requisitions, purchase orders, and requests for quotation
- Leads and opportunities, with calls, visits, and correspondence on the timeline
- Employee records and assignment history
- Projects and time entries, contracts and licenses, fixed assets and asset assignments, expense claims and support tickets
Doesn't move over or is set up again
- Passwords: they don't move over, for security reasons; users arrive inactive and become active when an administrator invites them
- Role and permission structure: rebuilt in the new IWB's permission model
- Signed e-Ledger files: archived on the old server for statutory retention, while the ledger certificate (berat) IDs carry over
04
What happens to your numbers
Statutory numbers such as invoice numbers, and the codes your team already knows, are kept. Document series in the new IWB start from a point that won't clash with the old numbers.
| Record | IWB Classic | New IWB |
|---|---|---|
| Sales invoice | Invoice number | Kept |
| Contact record | Company code | Kept |
| Product record | Material code | Kept |
| Employee | Employee ID | Kept |
| Quotes, orders, and purchasing documents | Document number | New series (TEK, SIP, SAT, SAS, STT); old number kept in notes |
05
Each migration is measured against the source
After every live migration, the source and the new system are compared and the result is saved. Earlier reports remain available too.
Coverage
Parts of the old system that hold data but have no counterpart in the new IWB are counted separately. If coverage for a module falls below 90%, a warning is raised.
Finance reconciliation
Debit, credit, and invoice totals from the customer and vendor ledgers are set side by side. If the difference exceeds the 0.1% threshold, it's recorded as a variance.
Accounting reconciliation
Debit and credit totals of journal entry lines, and any imbalances, are measured against the same threshold.
Link reconciliation
Shows how many of the migrated records' links to contacts, products, and documents are still intact.
The overall result is one of 4 values: clean, with warnings, incomplete, or not measured. "Not measured" doesn't count as clean.
06
Frequently asked questions
Is the new IWB an update to IWB Classic?
No. As announced on October 14, 2026, the new IWB is separate software. So we don't update your existing installation; we move your data into the new IWB.
Can we keep using IWB Classic after support ends?
Yes. You own your IWB Classic license, so you can keep using the software, but we don't recommend it. After November 30, 2026, IWB Classic won't be updated for regulatory changes and won't receive security patches. Storing and backing up the data on your own servers will also be your responsibility.
Who handles the migration, and how long does it take?
Our team runs the migration. How long it takes depends on the size of your database, the volume of attachments, and the reconciliation results, so we don't quote a fixed duration. We share our measurements with you after the trial migration.
Can we migrate while we keep using Classic?
Yes. The migration can be rerun, and each run processes only the records that changed. If you've corrected a record by hand in the new system, the migration doesn't overwrite it; it reports a conflict instead. Records deleted in the source also show up in the report.
Will we keep our old invoice numbers?
Yes. Invoice numbers, customer and vendor codes, product codes, and employee numbers carry over unchanged. Quotes, orders, and purchasing documents get new number series, with the old number kept in the document note. The new series start at a point that won't clash with the old numbers.
What happens to our e-Ledger and e-Invoice archive?
Ledger certificate (berat) IDs and line numbers carry over to the new IWB. Signed e-Ledger files, your electronic statutory books, stay behind; for legal retention, you need to archive them on your old server. If you use EDM as your integrator, past e-Invoices can be pulled from its archive.
How does migration work if we install the new IWB on our own server?
Our team runs the migration in this case too. We map out the plan with you in a meeting.