Contents
Where it is and who uses itBefore you startStep 1 — FirebirdSQL checkStep 2 — Source filePrepare backup as UTF-8 and connect / Test the connectionStep 3 — Table inventory and optionsStep 4 — Migration and progressStep 5 — Result and reconciliationMaintenance panelCommon errorsOn LinuxData migration from the old program (Firebird): Settings › Data migration
The data of your old program (FirebirdSQL) — customer and stock cards, invoices, delivery notes, cheques, recipes, images and documents — is moved into HNR after you sign in, from Settings › Data migration (from the old program). The First Setup wizard no longer migrates data. Only the system administrator sees the section; on a phone (Garden + Steps interface) the same flow opens step by step.
First create the company with the wizard: the data goes into a company that already exists; this section does not create a company. Back up the target company before the migration. The old program's database is read-only: not a single row changes during the migration.
Where it is and who uses it
Settings › Data migration (from the old program). Only the system administrator sees and uses the section; a user without the Administrator permission sees “Data import is available to system administrators only.” If the server is in read-only mode (write gate closed), the migration does not start.
The “Import data from an existing company” button in the First Setup wizard no longer migrates data; it only shows an information note: create the company first, then after signing in open Settings › Data migration.
On a phone (Garden + Steps interface) the same section opens step by step: each step is a separate screen, the buttons are large enough to tap comfortably, and tables appear as cards.
Before you start
- The target company must exist. Create the company with the First Setup wizard and sign in as an administrator.
- Back up the target company. The migration writes a large number of records to the company; keep a backup you can return to if something goes wrong.
- FirebirdSQL 3.0, 4.0 or 5.0 must be installed and running on this computer. Step 1 checks this.
- The old program's backup (.FBK) or database (.FDB) file must be reachable from this computer. If there is an image and document database (EK1), it should be in the same folder.
- Have the SYSDBA password ready (the default
masterkeyif it was not changed when Firebird was installed). If you will choose a backup (.FBK), leave free disk space of about 4 times the size of the backup.
Step 1 — FirebirdSQL check
When the page opens, it checks whether FirebirdSQL is installed on this computer, whether it is running, and which version it is. The old program's data is read with the FirebirdSQL on this computer: the server is this computer (localhost), the port is 3050 (or the RemoteServicePort value in firebird.conf if it was changed during installation) and the user is SYSDBA. None of these are asked; only the password is requested.
| Situation | What to do |
|---|---|
| Not installed. The screen says “Install FirebirdSQL first.” and you cannot continue. | Install FirebirdSQL 3.0, 4.0 or 5.0 from the “FirebirdSQL download page” link (firebirdsql.org) with the default settings (port 3050, SYSDBA); then press “Check again”. |
| Installed but the service is not running. The warning also shows the version and the port. | Open Windows Services and start the “Firebird Server - DefaultInstance” service; then press “Check again”. |
| Version not supported. The warning “This FirebirdSQL version is not supported” appears. | Install FirebirdSQL 3.0, 4.0 or 5.0. |
| Ready. A green frame reads “FirebirdSQL is installed and running”, with the version, localhost:port and SYSDBA. | Go on to step 2 with “Continue”. |
This step also shows the warning “Take a backup of the target company before importing.” If a migration was run before, the “Show result of the last import” button opens that result.
Step 2 — Source file
The Choose Files button opens the Windows file-open window. Select the old program's backup (.FBK) or database (.FDB); the .BAK and .GDB extensions are accepted too. A file of any other type is rejected (KAYNAK_DOSYA_TURU).
There is no second selection for EK1 (the image and document database; for example HESAP_EK1.FBK or HESAP.FDB_EK1.FBK): it is found automatically in the same folder, and “EK1 found” appears under your selection. If it cannot be found, the warning “EK1 not found, only the main file will be imported (images and documents are not imported)” appears; put EK1 in the same folder as the main file and choose the file again.
When HNR runs as a Windows service, the file is chosen with the browser's own file window. In that case select the EK1 file together with the main file (with the Ctrl key) in the same window. The selected files are copied, with a percentage indicator, into the migration folder on this computer (aktarim\kaynak); the original file is not touched.
Shortcut for large files: for backups of several GB, first copy the main file and the EK1 file into the migration folder on this computer (aktarim\kaynak; the full path is shown under the button before a file is chosen), then select only the main file with Choose Files. A file of the same name and size already in the folder is not copied again; the screen reads “The file was already in the import folder; it was not copied again.” and EK1 is found automatically in the same folder. Large files uploaded from the browser are sent in parts.
After choosing the file, only the SYSDBA password is entered. SYSDBA / masterkey are Firebird's initial values; if the password was changed when Firebird was installed, enter your own password.
Prepare backup as UTF-8 and connect / Test the connection
If you chose a backup (.FBK), the button becomes Prepare backup as UTF-8 and connect. The backup is opened on the server (“Restoring backup…”), converted to UTF-8 and its content is verified (“UTF-8 conversion and content verification…”); progress is shown with the number of tables and rows. The copy that passes verification is used as the source, and the original backup is kept. This job needs free disk space of about 4 times the size of the backup.
If you chose a database (.FDB), the button becomes Test the connection: it connects to the source and shows the version, the number of tables and whether EK1 was found. On success it reads “Connected · version … · … tables” and the Read the inventory button becomes active.
Step 3 — Table inventory and options
Read the inventory lists all the tables in the source; none is dropped silently. Each table comes with one of four decisions:
| Decision | Meaning |
|---|---|
| object | Cards/documents are built from the table and saved through the company's own write path (e.g. MUSTERI → customer card). |
| copy | If a table with the same name exists in the target, the common columns are copied row by row. |
| derived | Not copied: values such as the customer balance and the stock on hand are rebuilt by the write path. |
| skip | A system or log table. |
The migration options are set in the same step:
- Dry run (nothing is written): tries the migration without writing to the target; you see the counts and possible errors in advance. A dry run before the real migration is recommended.
- Also import the deleted-document archive and Also import historical movements: also carry over the old program's deleted-document backup and its historical movement tables.
- Import images and documents (EK1): if EK1 was found, it also carries over the image and document files.
- Continue even if the target already has data: if the target company already contains records, the migration stops by default (
HEDEF_DOLU); tick it only if you know what you are doing and have taken the backup. - Batch size: the number of records the migration processes at a time (1–5000, default 200).
Document numbers are preserved: the invoice, cheque and voucher numbers in the source stay exactly the same in the target. If the same source is migrated a second time, no duplicate records are written; existing ones are skipped.
Step 4 — Migration and progress
Start the import starts the migration on the server. The screen shows the stage, the percentage and the elapsed time, the card/document/written/skipped/failed counts per table, the number of files and the last lines of the migration log; if the engine uses several threads, their number and breakdown are shown too.
The migration runs on the server: the job does not stop even if you close this window or the browser. When you open the page again, the running migration is found and its progress is shown. Stop stops the job and shows “The import was stopped.”
Step 5 — Result and reconciliation
When the migration ends it says “The import has finished.” and the reconciliation table compares the source with the target: customer balances, stock on hand, cheques, invoices, recipes and files. Each row shows the item, source, target, difference and status (Matches / Deviation / Known deviation); the result per table, the duration, sample row errors and the numbers of automatic corrections are shown as well.
If the reconciliation shows a deviation, the screen says “Import finished — BUT the reconciliation shows a deviation.” and lists the deviating measures. Review the reconciliation table before using the migrated company; you can get the report as a PDF with the Legacy system reconciliation report · PDF button, or print it with Print.
Examples of rows that raised errors are listed under “Sample row errors”; if the migration cannot be completed, see the migration log for details.
Maintenance panel
The Maintenance panel under step 2 offers two operations:
- Repair open balances: if the remaining amount (open balance) is empty on the invoices that came from the old program, it is recalculated from the customer movements. A “Preview” is shown first and nothing is written (the number of invoices that will change, the previous and next totals, the skipped customers); if it looks right, press “Apply repair”.
- Reseed the dictionary: adds the missing rows of the interface translations; translations edited by hand do not change. It can take a few minutes; do not close this window.
Common errors
The error message shows the server's detail and, in parentheses, an error code; for example “Backup preparation tools are not configured on the server. — gbak/gfix not found (KAYNAK_HAZIRLIK_AYAR)”. Quote the code when you contact support.
| Code | Meaning and fix |
|---|---|
FIREBIRD_KURULU_DEGIL | “FirebirdSQL is not installed on this computer.” Install FirebirdSQL 3.0, 4.0 or 5.0 and press “Check again”. |
FIREBIRD_CALISMIYOR | FirebirdSQL is installed but its server is not running. Start the “Firebird Server - DefaultInstance” service from Windows Services and check again. |
KAYNAK_KIMLIK | “The source database user name or password was rejected.” Enter the SYSDBA password again; if the password was changed when Firebird was installed, enter that password (the default is masterkey). |
KAYNAK_HAZIRLIK_AYAR | “Backup preparation tools are not configured on the server.” If the detail says gbak/gfix not found, FirebirdSQL is not installed; if it says Firebird server not running, start the Firebird service. Check the installation and the service and try again; if it continues, pass the code on to the support team. |
KAYNAK_HAZIRLIK_DISK | “Not enough disk space to restore the backup and create a UTF-8 copy.” Free up about 4 times the size of the backup on the disk that holds the migration folder and try again. |
KAYNAK_YEDEK_GECERSIZ | “The file is not a valid Firebird FBK/BAK backup.” The file may be damaged or of another type; take the backup again from the old program and select it, or select the FDB file. |
KAYNAK_DOSYA_TURU | “Only a Firebird database or backup file can be selected (.fbk, .fdb, .bak, .gdb).” Select a file with a suitable extension; do not select the EK1 file as the main file. |
HEDEF_DOLU | “The target company already has records.” If the company has been used before, creating a new company is safer; if you will continue on purpose, take a backup first and tick “Continue even if the target already has data” in step 3. |
Only one migration can run in a company at a time (“A data import is already running for this company.”). If the server is in read-only mode (“The write gate is closed: the server is read-only right now”), the migration does not start.
On Linux
FirebirdSQL is installed from your distribution's package manager or from firebirdsql.org. The gbak and gfix tools must be in the PATH or under /opt/firebird; the remaining steps are the same as on Windows.
Related guides: Installation, Settings, Data cleanup.
Related guides
- Settings and Log — Making the Program YoursThe Settings window holds two kinds of setting side by side: those that are yours alone (theme, window layout, shortcuts) and those that affect company.
- Data Cleanup — A Guide from ScratchOver the years the same customer gets opened two or three times ("ABC Ltd. Şti." and "ABC LİMİTED ŞİRKETİ"), the same screw is entered under two different.
- I use it on my own: getting started in 10 minutesFor a small shop, workshop or freelancer using the program alone: the steps from installation to the first invoice and the month end.
- Practical User HandbookThis page is for an employee using the program for the first time and needing to complete daily work safely. Read the common rules here first.
- Your First Day — For People Sitting Down at the Program for the First TimeThis is the first page everyone should read and it takes ten minutes. We are not teaching accounting here, only how to drive the screen: how windows open.
- The Document Chain — The Backbone of the ProgramThis guide is not about one window but about the links between windows. The real gap in a newcomer's head is not "what does this button do" but "I sent a.