Import and manage hand data
Upload or paste histories, check results, recalculate records and manage databases.
On this page
Confirm the database
Open Hand & Action Analysis → Data Management and check the active database name. Importing, recalculating and clearing apply to this database regardless of analysis-page filters.
Upload files or paste histories
The import screen lists GGPoker, PokerStars and 888Poker and identifies records from their text. Coverage can vary by site, language, game variant and history version. Start with a small set of complete original records and inspect the result. Choose Upload and select TXT files, ZIP archives or a folder. Folder imports include recognizable files in subfolders. The app detects the source format. The wizard processes the source, parses records and writes them; wait for the final result.
For copied hand text, copy the complete history and choose Paste to read the clipboard. Avoid closing the window while records are being written. Cancelling requires confirmation; unfinished records may need another import.
Check the result
Read the new, recalculated, unchanged and failed counts separately, and inspect failed files. Percentages describe the current stage; completed parsing does not mean every record has been stored. Importing identical records again normally reports them as unchanged.
Open Hands afterward and check dates, hand numbers and contents. For a failure, retain the error and original file. A processed-file count alone does not establish a successful import.
Recalculate existing records
Choose Recalculate from original hand histories, then upload the original files or paste their text. You must supply the source histories; the database does not reconstruct the original files for you.
This rebuilds eligible older records and can add previously unseen hands. Duplicates already using the current statistics format stay unchanged. A pending count may describe the displayed sample rather than all missing EV or data. This operation does not force every historical calculation to refresh.
Files commit separately. A later failure or cancellation does not undo earlier committed files. Check new, recalculated and unchanged counts afterward.
Manage databases
Databases serve both bankroll and hand analysis. Create a nonempty, unique name of up to 40 characters, then select Use to switch. You can also rename a database. The default database cannot be deleted; switch away from an active database before deleting it. Deletion is permanent, so back up first.
Check before clearing
Clear Data in the Danger zone permanently deletes imported hands, derived statistics and related Cash observation samples and links in the active database. Manual bankroll records, confirmed results and tournament summaries remain. This differs from clearing bankroll records in Configuration. Date, position and game filters do not narrow the operation. Back up first, confirm the database and retain the original histories separately.
The upgrade notice's Clear and re-import also deletes uploaded bankroll results, including tournament summaries, while retaining manually entered sessions. Clearing happens before the import wizard opens. Cancelling or failing afterward does not restore deleted data. Use it only with a backup and the original files available.
Import troubleshooting
For empty or unrecognized clipboard content, copy a complete hand history again. For archive or file failures, inspect the filename and reason in the result. To retrieve GG files again, use the GG import guide to compare download batches with actual additions.
Handle text that could not be parsed
After a GG import encounters unparsed text, the app may offer to share it. Choose Not now to keep your source files and inspect the import result. If you choose Review and share, review the listed failed text and files, add a useful note and then confirm sending. Import failure alone does not upload the text. Check for personal information and reduce the selection if it exceeds the size limit. Sharing helps investigate parsing; it does not automatically repair the database.
