Import Inventory Data

Inventory import is normally used when a new account is being prepared and existing stock, items, locations, serial numbers, or historical inventory data need to be brought into the system before daily operations begin.

Because different customers have different source data, FlightLogger Maintenance supports several import methods. The correct method depends on the format and purpose of your source file.

Why inventory import matters

Inventory data is used throughout FlightLogger Maintenance.

It affects:

• stock availability
• purchasing decisions
• reservations
• pick lists
• work order preparation
• serialized item tracking
• batch traceability
• audit history
• component and maintenance readiness

For that reason, inventory import should be treated as an implementation step, not just a file upload.

Before importing, it is important to understand what kind of data you have, what the import is expected to create, and whether the data represents current stock, item master data, serialized units, or historical movements.

Import methods

FlightLogger Maintenance supports several inventory import paths.

The main import methods are:

• Initial Data Import
• Legacy Stock Import
• AcMP Import
• AcMP Transaction Import

Each import method is designed for a different source format.

Initial Data Import

Use Initial Data Import when your data is prepared in structured CSV or Excel files.

This is the most controlled and template-based import method. It lets you upload separate files for each data type.

Initial Data Import can import:

• units of measure
• inventory items
• locations
• stock counts
• serialized items

This method is best when you can prepare your data using the FlightLogger Maintenance templates, or when your data can be exported from another system and cleaned into a structured format.

Initial Data Import is especially useful when you want control over each import step.

For example, you may import units of measure first, review the result, then import items, then locations, then stock counts.

Legacy Stock Import

Use Legacy Stock Import when your existing data is stored in one combined legacy Excel stock file.

This import method is designed for files where multiple types of inventory data are mixed together in the same spreadsheet.

Legacy Stock Import can extract and create:

• inventory items
• locations
• stock counts
• serialized items
• batches
• suppliers

This method is useful when the legacy file contains columns such as part number, description, quantity, location, rack, shelf, bin, compartment, serial number, batch number, supplier, unit price, and expiry date.

Unlike Initial Data Import, you do not split the source data into several template files. FlightLogger Maintenance reads the Excel file and separates the data into the relevant inventory records.

AcMP Import

Use AcMP Import when your source data is an AcMP Excel export.

AcMP Import is specifically designed for AcMP catalogue-style exports. It understands AcMP column names and maps them into FlightLogger Maintenance inventory records.

AcMP Import can handle:

• store or parts catalogue exports
• serialized catalogue exports
• part numbers
• descriptions
• stock quantities
• main locations
• minimum and maximum stock levels
• serialized inventory
• alternate part numbers
• certificate requirements
• supplier and purchase references

This import method should be used when the source file comes from AcMP. Do not use Initial Data Import for AcMP files unless the data has first been converted into the FlightLogger Maintenance template format.

AcMP Transaction Import

Use AcMP Transaction Import when you have an AcMP movement export and want to import historical inventory movements.

This is different from importing catalogue data.

Catalogue imports create opening inventory data, such as items, locations, current stock, and serialized units.

Transaction imports replay movement history. This means the import creates inventory transactions based on AcMP movement rows such as:

• IN
• OUT
• CORR

Use this method when you want receipts, issues, and corrections from AcMP to be represented as inventory ledger entries in FlightLogger Maintenance.

This can be important when you need historical inventory usage and movement traceability, not just current stock levels.

Choosing the right import method

Use this guide when deciding which import method to use.

If you are unsure which method to use, review the source file format first. The source format is usually the deciding factor.

Setup mode

Inventory imports are intended for the setup phase.

The import features require setup mode to be enabled for the account. If setup mode is not enabled, FlightLogger Maintenance will not allow the import to run.

Setup mode helps protect operational data because imports can create or update many records at once.

Before importing, make sure:

• setup mode is enabled
• the source files are ready
• the import method matches the source format
• the user running the import has the required permissions
• the data has been reviewed before upload

After the implementation import is complete, setup mode can be disabled by a root user.

Import order

The correct import order depends on the method you use.

For Initial Data Import, the recommended order is:

1. Units of measure
2. Items
3. Locations
4. Stock counts
5. Serialized items

For Legacy Stock Import, the system extracts multiple record types from one Excel file, so the import handles the internal processing order automatically.

For AcMP catalogue import, the system reads the AcMP export and maps the catalogue or serialized catalogue data into the relevant records.

For AcMP transaction import, movement files should be imported in a sensible operational order. If receipts and issues are split across files, import receipt movements before issue or correction movements so the stock history is easier to validate.

Data that should be reviewed before import

Before importing inventory data, review the source data carefully.

Pay special attention to:

• part numbers
• descriptions
• units of measure
• item types
• locations
• stock quantities
• serial numbers
• batch numbers
• supplier names
• certificate requirements
• dates
• costs
• expiry dates

Small issues in source data can create unnecessary cleanup after import.

For example, inconsistent part numbers may create duplicate items, missing locations may prevent stock from being imported correctly, and duplicate serial numbers may cause serialized rows to be skipped or reported as errors.

What happens after import

After an import runs, FlightLogger Maintenance shows an import result page.

Depending on the import method, the result page may show:

• records created
• records updated
• rows skipped
• row-level validation errors
• stock count errors
• serialized item errors
• supplier errors
• batch errors
• transaction import exceptions

Always review the result page before continuing.

An import may complete even if some rows contain errors. This allows valid rows to be imported while problem rows are reported for review.

Common import mistakes

Using the wrong import method

Do not upload an AcMP export into Initial Data Import unless it has been converted to the correct template format.

Do not use Legacy Stock Import for clean template-based data.

Choose the import method based on the source file.

Importing stock before items and locations exist

Stock counts require existing items and locations.

If items or locations are missing, stock rows may fail validation.

Importing serialized items before serial tracking is enabled

Serialized items require the related inventory item to support serial tracking.

If the item is not configured for serial tracking, the serialized item row may fail.

Ignoring row-level errors

The import result page should always be reviewed.

Even if the import completes, some rows may need correction.

Importing into an account already in daily use

Initial imports should normally be completed before operational inventory work begins.

If the account is already live, coordinate carefully before importing data that may affect stock, batches, or serialized inventory.

Best practice

A good inventory import process is usually:

1. Identify the source system and file type.
2. Choose the correct import method.
3. Review and clean the source data.
4. Enable setup mode.
5. Run the import.
6. Review the result page.
7. Correct any errors.
8. Re-import corrected data where appropriate.
9. Validate inventory records in FlightLogger Maintenance.
10. Disable setup mode when implementation import is complete.

Inventory import is not only about moving data into the system. It is also a quality check before the account starts using FlightLogger Maintenance for daily inventory control.