1. Inventory your companies, sites, and custom workflows
Ask your IndySoft administrator which companies, groups, and records your export account can see. Choose a sample site and note any records that also appear under another company. Find two instruments with similar display identifiers. Check whether the combination of company and equipment identifier, or another stable source key, is needed to identify each one uniquely.
List custom fields, multiple schedules per asset, reviewer roles, and events you must keep. A destination field map does not recreate a configurable IndySoft workflow. Back up the source through your approved procedure and keep access to the steps, certificates, signatures, and attachments that are not going to move with the asset register.
2. Export equipment and history as separate data sets
In IndySoft EAM, use a saved Equipment grid or report that includes the identifiers, location, and schedule your pilot needs. The documentation describes Excel output and data-only columns for certain report layouts. Export the rows in a data-friendly format and save a UTF-8 CSV copy if your edition does not offer CSV directly. Check that site and company filters match your migration scope.
Export the relevant events or history from a separate view or report, retaining the same equipment key and a distinct event key. Confirm with your administrator which event fields your layout exposes. Some native Export/Import options use structured files such as XML, not simple CSV. Preserve the native export and original attachments separately, even when you build working CSVs for equipment and history.
3. Build the equipment field map
Use a working file that preserves text IDs and decimal precision and expresses dates as YYYY-MM-DD. IndySoft captions and field layouts can vary by company. Look at actual values and confirm which field is your durable equipment identifier before choosing an asset tag. If two sites reuse identifiers, create unique destination tags and retain the original keys in a separate cross-reference rather than losing them.
The planned CaliberOS wizard would preview a CSV, align headers to the asset register, and let you review exceptions before importing. It is not available today. Scope a manual pilot or discuss the export with us. Where IndySoft has multiple calibration schedules for one asset, do not silently pick one; record the decision and retain the other schedules in the approved system.
| IndySoft field | CaliberOS field | What to check |
|---|---|---|
| Equipment ID (actual identifier) | Asset tag | Confirm the field behind the display caption. Add a site prefix if approved and needed for uniqueness. |
| Serial Number | Serial number | Keep exact text; verify it is separate from the equipment ID in your layout. |
| Company / Site / Location | Location | Use a consistent readable location and keep the original key in the cross-reference. |
| Manufacturer / Model | Make / Model | Map each independently; flag missing or combined values. |
| Calibration frequency + unit | Interval (months) | Map only the approved whole-month schedule. Keep usage- or day-based exceptions separate. |
| Next Due (approved schedule) | Next due date | Resolve multiple schedules first. Preserve the actual due date. |
| Event history / signed report | Separate controlled archive | Preserve original event keys and evidence; not imported with the asset record. |
4. Reconcile equipment and event totals by site
Write down source equipment, exported equipment, unique keys, and approved rows for each company and site. Compare those counts to equipment actually entered, held, or skipped. Do not reconcile only the combined total: a missing asset at one site can be masked by a duplicate at another. Put every mismatch into an exception list with a reason and owner.
Verify a sample of serials, site names, interval units, and dates. Count events separately and compare records per equipment key, checking a repaired or overdue instrument and a certificate amendment. Use the due-date calculator as an independent check on a simple monthly asset, not as proof that a migrated due date or interval was approved.
If your counts disagree, check permission filters and date ranges before editing any records. Repeated report headers and subtotal rows can also make a CSV look bigger than the real register.
5. Close the pilot before talking about cutover
Have someone at the pilot site find an asset by its new tag, then locate the old record through the cross-reference. Have a reviewer open an original report and confirm they can still see its release status, signer, if applicable, and linked events. Document where approval routes or access boundaries differ. Ask both people to repeat the steps using only the written handover notes.
Only expand after exceptions are understood and the team agrees on what stays in IndySoft. Plan how late edits will be captured during the transition, who signs off, and what would trigger a rollback. Keep retention, backups, and retrieval under your controlled procedure; do not treat a CSV conversion as a complete replacement of your source records.
References: IndySoft EAM Equipment grid and report documentation · IndySoft EAM export options · IndySoft EAM history documentation.