Skip to main content

Lansweeper import

Lansweeper import brings discovered assets into Starhive, so they can be enriched with complementary data — owners, vendors, locations, compliance controls — in one place.

1. Set up your Starhive types​

Decide which Lansweeper asset types and fields you actually want — importing only the frequently used fields, and linking out to Lansweeper directly for the rest, keeps this manageable. Create a Starhive type per Lansweeper asset type, with attributes to receive the mapped fields, plus any supplementary attributes you need.

2. Configure the Lansweeper source​

  1. Imports → Lansweeper, and give it a descriptive name.
  2. Get a Lansweeper Data API token (see Lansweeper's developer docs).
  3. Create Source — Starhive scans your Lansweeper workspace schema. This scan re-runs every time you modify the source, so schema changes on the Lansweeper side are picked up automatically.

3. Configure streams​

For each Lansweeper data stream you want:

  1. Create connection, and pick the stream and the corresponding Starhive type.
  2. Map each Lansweeper field to a Starhive attribute — for a Reference attribute, also choose which attribute on the referenced object should match (its Reference identifier), e.g. mapping assetCustomer_manufacturer to that type's Name attribute. Leave non-mandatory fields unmapped if you don't need them.
  3. Create Connection, and repeat for every stream you need.

4. Run the import​

Click the sync icon, select which streams to run, and choose Manual or Scheduled (from the ⋯ menu → Scheduled → pick an interval → Save).

Starhive automatically sequences imports when destination types depend on each other — e.g. if a Server type references an OS type, OS objects import first so Servers can link to them correctly.

For import errors, see Import error reports.