Data Imports

Who does this: System Administrator

There are two ways to get your data to us:

• Recommended — Support Contact: Use the Support Contact feature in Musket (top-right user menu → Support contact). Describe what you are sending and attach your data file(s) directly in the panel (up to 20 MB per submission). For larger datasets, mention this in your request and our team will arrange an alternative transfer method.
• Alternative: You can also reach us through the contact details shown in the Support Contact panel inside Musket.

Musket can work with any structured format that can be reliably read and mapped:

• Excel workbooks (.xlsx, .xls)
• CSV files (.csv)
• SQL database exports (from your previous system's database)

For a successful import, your data must be consistently formatted:

• Dates must use a single consistent format throughout (e.g. DD/MM/YYYY — not a mix of formats).
• Identifiers — such as staff names, registration numbers, or ID/passport numbers — must be consistent throughout the dataset. Mismatched identifiers prevent records from being linked correctly.
• Data cleanup (fixing inconsistencies, filling in missing fields) is the client's responsibility before submission. We do not include data cleanup as part of the import service.

The following types of historical data can be imported into Musket. Each import is evaluated individually — depending on data completeness and consistency, a full or partial import may be possible.

• Historical Flight Schedules — past flight records, including crew assignments and aircraft used.
• Historical Reports — safety, security, dangerous goods, ad-hoc, and other report submissions.
• Historical Notifications & Tags — past notifications issued to staff.
• Historical Findings & Corrective Actions — past findings and CARs from audits or reports.
• Historical Logbook Data — airframe, engine, and propeller logbook records.
• Audit Checklists — pre-existing audit checklists from your documentation (e.g. from a Word or PDF source that can be structured into a table format).

Additional data types not listed above are evaluated on request — contact support to discuss.

• Imports are evaluated case-by-case. Musket Support will review your dataset and advise on feasibility, any preparation required, and timelines before proceeding.
• Missing critical fields or inconsistent identifiers (e.g. crew names not matching existing user records in Musket) may prevent a full import and will require corrections on your side first.
• Allow reasonable time for complex datasets — large or multi-type imports take longer to process and validate.
• Imports are a one-time service during onboarding. Ongoing data entry is done directly in Musket.

To get started: Contact Support

• Integrations — connect Musket with third-party systems and booking platforms
• Introduction — return to the overview of all setup areas