VauPrime Docs
VauPrime DocsAdvanced FeaturesBUSY Import & Export
Advanced FeaturesCurrent app behaviorDart-source backed

BUSY Import & Export

An implementation-based guide to both BUSY workflows in VauPrime: importing exported BUSY masters and transactions, and exporting selected VauPrime financial-year records as files ready for BUSY import mapping.

Import source

BUSY exports

Use Master Export and Transaction Export

Import sections

2 tabs

Configuration and Preview & Import

Plan requirement

Elite+

At least Elite to run BUSY import

Export format

Mapped input files

Not a native BUSY company backup

What is BUSY Import & Export?

Purpose and current behavior of this feature.

VauPrime supports distinct BUSY data import and export screens. The import screen uses exported files from BUSY, not a mandatory local HTTP connection; the export screen writes spreadsheet-style input files derived from VauPrime records for mapping and import into BUSY.

For accurate imports, the native app explicitly recommends TWO BUSY files: Master Export and Transaction Export. Importing only transactions can leave the account group hierarchy incomplete. Select a format and files, let the parser analyze the data, review group and voucher compatibility and financial year availability, then perform the validated import.

The separate BusyExportScreen loads financial years from the organization, lets users choose categories and writes the selected data using BusyExportService. The output requires the target BUSY user to configure field-to-column mapping; it is not represented as a native BUSY company backup or lossless round-trip.

Android UI structure

Screen-by-screen structure, tabs, lists, taps and action behavior on Android.

Responsive importerThe BusyImportScreen explicitly supports Android with GlobalHeader and main content, without a desktop sidebar.
Guide on openingAn initial sheet offers Busy Import Guide and recommends Master Export plus Transaction Export.
ConfigurationChoose a supported format and import type, and select exported BUSY files.
File pickerThe picker accepts selected-format files, allows multiple files and limits each selection to the first five.
Preview & ImportInspect parsed summary cards, a detailed data table, compatibility and field-validation reports before proceeding.
Financial-year requirementImport is blocked when the required financial year has not been configured compatibly.
Import confirmationReview the confirmation state and start the validated import after data has been parsed.
Progress and errorsShows progress and individual error handling. Review errors instead of assuming all parsed rows were inserted.

Windows UI structure

Desktop layout, wide-screen controls, tables and row actions on Windows.

Desktop shellWindowGlobalSidebar and GlobalHeader wrap the importer workspace on Windows.
Two main tabsConfiguration and Preview & Import are implemented through the shared CentralizedTabBarView.
ConfigurationChoose the format and import type, upload BUSY exports, and review recognition and analysis.
File validationThe screen can show field validation, BUSY compatibility analysis and duplicate-conflict prompts.
Preview tableAn expandable detail table shows parsed records and category counts.
Import executionThe importer checks duplicate masters and voucher numbers, preloads mappings and processes data by category with progress tracking.
BUSY Export screenA separate BusyExportScreen lists available financial years, selected master/voucher categories and an Export action. It displays the saved path after success.
Export category selectionAccounts, Account Groups, Products, Units, Material Centers, Sales, Purchase and Payment / Receipt / Journal / Contra are explicitly supported by the export service.

Import and export configuration details

Fields and behavior taken from BusyImportScreen, BusyExportScreen and their processing services.

Master ExportBUSY masters file: groups, accounts and related reference data. Import this with the transaction export for complete relationships.
Transaction ExportBUSY transactional data: supported sales, purchases, payments, receipts, journals, contra, notes and stock journals.
Choose FormatPick file type before opening the file picker. The picker defaults in source to dat, xml, xlsx, csv and json if no format was selected, but the UI requires selection first.
Maximum selected filesUp to five files from a single file selection. Each selected file displays its name, approximate size and modified date.
Import TypeThe importer has a separate import-type field beside the format; it controls the parsing workflow.
Preview & Import tabShows parser results, expandable preview tables and import confirmation controls.
Financial-year validationChecks destination financial-year compatibility before import. Create the missing financial year in VauPrime before proceeding.
Group and account mastersParses groups and accounts; parent-chain and transaction-account dependencies are checked so the imported hierarchy is meaningful.
Products and unitsParses stock products, measurement units and material centers; mappings depend on source data.
Brokers and bill sundriesDedicated import routines exist for brokers and bill sundry data, with mapping and replacement logic.
Sales and purchaseDedicated parsers and import services handle voucher data, accounts, items and duplicate voucher conflicts.
Credit and debit notesParsed note types are handled by dedicated import routines.
Payment, Receipt, Journal and ContraThe import screen collects category-specific transaction inputs for the supported voucher types.
Stock JournalDedicated parser and import routine supports stock journal records when present.
Duplicate checksBusyDuplicateChecker compares groups, accounts, products, brokers, sales and purchases before import; duplicate voucher numbers are resolved separately.
Import subscriptionBusy import calls SubscriptionPlanAccessService.isAtLeastElite; otherwise an Elite Plan Required upgrade sheet appears.
Export financial yearThe BUSY export screen requires an existing selected financial_years record for the destination organization.
Export categoriesMaster tables: Accounts, Account Groups, Products, Units, Material Centers. Voucher categories: Sales, Purchase and Payment / Receipt / Journal / Contra.
Export validationBUSY export needs authentication, a valid organization ID, selected financial year, at least one category and valid date range.
BUSY export outputGenerated spreadsheet-style files require importing and field-to-column mapping inside BUSY. They are NOT a native backup or direct live sync.

Step-by-step BUSY import and export

Follow the current in-app flow from start to completion.

01

Back up both companies

Make a backup of your BUSY source data and your VauPrime destination before changing records.

02

Export BUSY masters and transactions

Prepare both Master Export and Transaction Export. A transactions-only transfer can result in missing group hierarchy.

03

Open BUSY Import

Select the VauPrime organization and open Settings / Import Export → BUSY Import.

04

Select import format and type

Choose a file format, then the type of BUSY data you are importing.

05

Select BUSY files

Choose up to five supported exported files. Verify the selected names and format recognition.

06

Review preview and compatibility

Open Preview & Import, examine the parsed tables, field-validation results, financial-year compatibility and missing master mappings.

07

Resolve duplicates

Handle duplicate group/account/product/voucher conflicts and verify voucher dates before proceeding.

08

Start import and review results

Confirm import. Inspect the progress and success/error feedback, then compare master totals and voucher counts with BUSY.

09

To export, open BUSY Export

In the separate export screen, select the VauPrime organization and an available financial year.

10

Choose categories and export

Select needed master and voucher categories and export. Find the saved file path, configure the field mapping in BUSY and validate the imported result there.

Validation and common checks

Checks and restrictions applied by the current screen.

A BUSY import is not a guaranteed complete migration. Source structure, parsing compatibility, missing masters and duplicate records can affect the result.
At least Elite plan is required for the BUSY import action; export prerequisites are enforced separately by BusyExportService.
The app explicitly recommends uploading BOTH Master Export and Transaction Export. Importing transactions alone can omit group relationships.
The import file picker needs a selected format and accepts up to five files per selection.
An incompatible or missing destination financial year blocks import until resolved.
Duplicate records are checked and can block import; duplicate voucher-number conflicts have separate resolution handling.
Import actions process categories and handle errors; a partial failure does not establish an all-or-nothing rollback of every inserted record.
BUSY export validates organization, user, financial year, categories and reporting dates. Output is not a native BUSY company backup or proof that BUSY accepted its import.
Cross-software account, unit, tax, voucher and date mappings must be verified in the destination.

Important behavior and notes

Details worth knowing before using the feature in daily work.

Inspected source files: lib/screens/Settings/ImportExport/Services/Busy/busy_import_main.dart; ParsingServices/*; Export/busy_export_screen.dart; Export/busy_export_service.dart.
BUSY Import is implemented for both Android and Windows in the same Flutter screen. Windows includes the global sidebar while Android uses a full-width content layout.
The BUSY importer is file-based; although busy_port_service.dart also contains optional host/port connection helpers, a local port is not a required precondition of this file-import workflow.
The import processing code clears session duplicate caches before running and checks duplicate masters and voucher numbers.
The export service generates configurable BUSY Excel/CSV style import inputs and explicitly states that the target user must perform BUSY field-to-column mapping.
A destination financial year and the selected categories govern the exported data. Validate account references and source dates before using it.
Worked example: choose Accounts, Products and Sales for FY 2026–27, export the mapping-oriented files, then map BUSY's required fields before running the BUSY-side import. A successful VauPrime file creation does not guarantee a successful BUSY data import.
The marketing page at www.vauprime.com/busy-import-export is informational, not an upload or transfer endpoint.