User instructions
Export and import project workspaces
Take the saved work you need to another PC
Open Admin → Projects → Export — choose contents…. This screen now lists every current workspace, not just reusable checklist setup. Save unfinished work, stop the hub and make a backup before transferring.
| Transfer choice | What is saved |
|---|---|
| Complete project | All saved workspaces, history and database-held files. This includes the newer Inventory, Tasks, Maintenance, Toolbox Talks, Certificates and asset features. |
| Selected workspaces | Only the selected workspaces and their required supporting workspaces. These are history-bearing project copies, not blank templates. |
| Reusable setup | The separate checklist setup workflow provides unpublished checklist templates, source documents and selected user/department setup, without completed checklist records. Other workspaces have their own library export controls. |
Choose the contents
- Choose Complete project for a whole-project handover. It is selected by default. Review the workspace counts, including empty sections.
- Or choose Selected workspaces, then tick Checklists, Logs, Inventory, Stock verifications, Private tasks, Maintenance, Toolbox Talks, Asset profiles and pictures, Certificates or Original documents.
- Required supporting workspaces are included automatically and identified below the selection. Dependencies include entire workspaces, not only linked items. For example, certificates require inventory and asset profiles; private tasks require their verification results and inventory.
- Review the privacy confirmation and choose Save project export…. The file ends in .ajproject. Your source project is unchanged.
What each workspace includes
| Workspace | Included content |
|---|---|
| Checklists | Types, drafts, saved records, readings, approvals and completion photographs, with supporting original files. |
| Logs | Logbooks, entries, correction history, references and pictures. Linked checklist records and their originals travel too. |
| Inventory | Lists, item records, nested boxes, locations, custody and movement history. |
| Stock verifications / Private tasks | Shared verification results, or private tasks with their assignments, reviews, results and access requirements. Unselected private verifications are not converted into shared ones. |
| Maintenance | Routines, work orders, saved steps, approvals and evidence photographs, plus supporting inventory and originals. |
| Toolbox Talks | Reusable forms, saved briefings, participant and witnessed-guest acknowledgements, and history. |
| Asset profiles and pictures | Equipment identification pictures, asset notes, responsible contacts and low-stock rules, with the inventory they describe. |
| Certificates | All saved certificate revisions, original attachment files, date rules and links to assets. |
| Original documents | The complete original-file library, including unlinked or restricted files. Review it before sharing. |
Calendar events and current date/low-stock alerts are generated from the retained dates and rules. There is no separate calendar database to select. Shared user and department history is retained even when some workspaces are omitted.
Import as a new project
- On the destination PC, open Projects → Import — choose contents… and select the .ajproject file. Review the actual saved contents and counts.
- Keep Complete project to import everything in that file, or choose a smaller supported selection. You cannot recover work that was omitted when the file was exported.
- Confirm the contents and select Continue to new project…. Give it a name and a new or empty data folder. An existing project is not overwritten or merged.
- Open the imported project and sign in using an enabled administrator account from the export. Configure the destination’s approved network address and trusted connection separately.
- Check saved records, attachments, assignments and reports before using it operationally. Coordinate the handover: two independent copies do not synchronise automatically.
Imports use a new project identity. QR labels linked to the previous project may need to be generated again. A historical project with additional unrecognised tables can be transferred in Complete mode; a selective transfer stops rather than guessing which data to omit.
Transfer reusable definitions instead
For checklist-only setup, choose Need reusable setup without operational history?… in the export window. This is the earlier setup importer/exporter, kept for compatibility; it is not the all-workspaces project handover. It can provide new unpublished checklist drafts, original files, disabled Technician profiles without transferable passwords, department definitions and suggested defaults. Review mappings and assign local reviewers before enabling accounts or publishing.
For a Logs definition, Inventory structure/current-item package, or Toolbox form, use that workspace’s own export option. Those formats are deliberately narrower: do not use them as a substitute for a full backup of certificates, asset pictures, maintenance or task history.
Fleet and manifest dependencies
Vessels and manifests now appears in the project-workspace selector. Inventory and Fleet depend on each other so a selected inventory transfer cannot drop recorded custody or shipment history. Fleet also retains the supporting asset profiles, certificates, maintenance and source documents. Dependencies include whole workspaces, not just the shipped rows.
Complete project copies and complete backups retain all fleet tables, original shipping files and history. Narrow Inventory structure/current-item packages cannot retain this complete fleet evidence: exporting allocated item rows through that format is blocked. Use a full or dependency-aware project transfer. Structure-only inventory export remains available.
Vessel log scope in transfers
Complete project copies retain logbook-to-vessel links, per-user site log rights and their access-change history. A history-bearing selected Logs transfer includes these with the retained site directory and accounts; omitting Logs omits its scope and rights too. The transfer remains administrator-only, unencrypted and not filtered to a single vessel.
A standalone .ajlogs export transfers a logbook without vessel grants. It imports as a new project-only logbook. Review its content and deliberately link it to a local vessel and users before using it in the vessel portal. It does not modify or restore the original scope automatically.