Asset Management: import from your current asset system
An org owner or admin imports from Setup, Import. Import in this order, because later files refer to earlier ones: locations, then assets, then preventive maintenance schedules, then work-order history, then meter readings.
1. Export each list from your current system as CSV. Many asset systems use column names such as ASSETNUM, SITEID, LOCATION, DESCRIPTION, STATUS, PMNUM, FREQUENCY, FREQUNIT, JPNUM and WONUM, and the import accepts them as they are. You can also download Turtini's own template header for each list.
2. Choose the list type, then paste the file or choose it.
3. Read the preview before you commit:
- which column became which field;
- every column the import did not use, listed by name rather than dropped;
- each row that will be created or updated;
- each row that will be refused, with its line number and the reason (an unknown status, a parent that is not in the file or the registry, a date it cannot read);
- each assumption, such as a schedule with no fixed or floating mode, which is imported as floating and says so.
4. Commit. Refused rows are skipped and listed again; nothing is half-written.
Notes:
- Records are matched on their key (location code, asset number, PM number, work order number), so importing the same file again updates rather than duplicates.
- A site named in SITEID that does not exist yet is created as a site location.
- Parent references resolve within the file in any order. A parent loop is refused.
- Dates are read as YYYY-MM-DD or M/D/YYYY. Anything else is refused, never guessed.
- Imported work-order history keeps its labor hours and costs as totals.
- An import never overwrites a work order created in Asset Management.
- Up to 5,000 rows per file. Split a larger export.