Skip to main content
Solved

Bulk Export to Correct and Bulk Import

  • Feb 25, 2026 10:40 PM UTC
  • 5 replies
  • 816 views

Forum|alt.badge.img+1

Hello all!

I’ve exported all of the Assets I currently have at a specific Location in order to do some admin cleanup (e.g. fill in missing fields, standardize Asset Types and naming conventions, etc). I imported the .csv file into Google Sheets to edit what I need, but I want to make sure that when I upload this after I’m done that it will NOT duplicate the assets as “new.” The .csv file DOES list the Asset ID as one of the fields, so I would assume it would be fine, but I want to make sure. This location is a test bed for correcting all of our locations throughout our CMMS, but it still has 200+ assets and sub-assets, and I’d really like to NOT cause more work for myself.

Thanks in advance!

Best answer by derekwills

UPDATE: I ran a test, and it appears it absolutely does treat any bulk import as newly created assets. In MaintainX, I created a Test Parent Location with two Test Sub Locations. Each Sub Location had 1 Test Parent Asset, which had 3 Sub Assets. I deliberately made naming convention issues, and left all of the detail info blank. This gave me 8 Test Assets when I exported the .csv file for that location. I imported the file into Google Sheets, corrected all of the deliberate errors and missing fields with information, then went to import it. As soon as I saw that the ID field was unmatch during the import process, I knew the answer, but proceeded anyway. Sure enough, once I completed the bulk import, that Test Location went from having 8 Assets/Sub Assets to having 16.

 

This might not be a huge deal personally for my particular use case, but having come from being a maintenance manager in manufacturing in the past, this would be a HUGE issue for data cleanup because it ultimately means that the CMMS admin will either have to tediously edit each and every asset currently in the system in order to preserve all of the history assigned to them, or lose all of that history by doing a bulk import of all of the corrections, and then deleting the previous assets.

 

This should be a relatively easy fix for the MaintainX devs to add a feature that checks for the ID field during the upload, and compares it to the current database. Any matching IDs would be highlighted during the import process, and they can even simply add a feature to confirm overwriting the previous asset info with the new uploaded one. I know building and coding new features does take time, but for users whose use case requires the preservation of all WO history and downtime tracking, this feature would make data cleanup much simpler for their application, and would be a huge value add.

View original

5 replies

Forum|alt.badge.img+1
  • Author
  • Emerging Technician
  • Answer
  • Feb 26, 2026 3:38 PM UTC

UPDATE: I ran a test, and it appears it absolutely does treat any bulk import as newly created assets. In MaintainX, I created a Test Parent Location with two Test Sub Locations. Each Sub Location had 1 Test Parent Asset, which had 3 Sub Assets. I deliberately made naming convention issues, and left all of the detail info blank. This gave me 8 Test Assets when I exported the .csv file for that location. I imported the file into Google Sheets, corrected all of the deliberate errors and missing fields with information, then went to import it. As soon as I saw that the ID field was unmatch during the import process, I knew the answer, but proceeded anyway. Sure enough, once I completed the bulk import, that Test Location went from having 8 Assets/Sub Assets to having 16.

 

This might not be a huge deal personally for my particular use case, but having come from being a maintenance manager in manufacturing in the past, this would be a HUGE issue for data cleanup because it ultimately means that the CMMS admin will either have to tediously edit each and every asset currently in the system in order to preserve all of the history assigned to them, or lose all of that history by doing a bulk import of all of the corrections, and then deleting the previous assets.

 

This should be a relatively easy fix for the MaintainX devs to add a feature that checks for the ID field during the upload, and compares it to the current database. Any matching IDs would be highlighted during the import process, and they can even simply add a feature to confirm overwriting the previous asset info with the new uploaded one. I know building and coding new features does take time, but for users whose use case requires the preservation of all WO history and downtime tracking, this feature would make data cleanup much simpler for their application, and would be a huge value add.


Katja K
Forum|alt.badge.img+2
  • MaintainX Community Team
  • Mar 12, 2026 4:02 PM UTC

Hi Derek ​@derekwills,

Thank you for taking the time to run such a thorough test and document your findings. I agree that using IDs to update existing assets rather than duplicate them would be a major improvement. 

I’d encourage you to share this directly with MaintainX Support or your Account Manager, so they can formally log the request with our Product team for consideration. Feedback like yours plays an important role in shaping future improvements.

Thanks again for sharing your experience and suggestions with the community! 😊


JohnStraight
  • Emerging Technician
  • Apr 2, 2026 6:02 PM UTC

Hi Derek ​@derekwills,

Thank you for taking the time to run such a thorough test and document your findings. I agree that using IDs to update existing assets rather than duplicate them would be a major improvement. 

I’d encourage you to share this directly with MaintainX Support or your Account Manager, so they can formally log the request with our Product team for consideration. Feedback like yours plays an important role in shaping future improvements.

Thanks again for sharing your experience and suggestions with the community! 😊

Agreed. I am in manufacturing, just started at a new plant, and this is an issue across Assets and Parts


  • Emerging Technician
  • Oct 27, 2026 12:59 PM UTC

Hi Derek ​@derekwills,

Thank you for taking the time to run such a thorough test and document your findings. I agree that using IDs to update existing assets rather than duplicate them would be a major improvement. 

I’d encourage you to share this directly with MaintainX Support or your Account Manager, so they can formally log the request with our Product team for consideration. Feedback like yours plays an important role in shaping future improvements.

Thanks again for sharing your experience and suggestions with the community! 😊

Any update on this? Has it been implemented?


  • Emerging Technician
  • Nov 4, 2026 5:30 PM UTC

I will add my two cents to this as well. I am currently trying to fix a messy asset list with bad formatting, incomplete data, and duplicates. Being able to go back to the .csv and fix it without creating all the duplicates and loosing all the meta-data would be extremely advantageous.

I just started at a legacy manufacturing facility that started using MaintainX about 1.5 years ago and are still trying to get everything added and setup. Having set up MaintainX at a previous employer, I was tapped to help fix the data that has already been added and getting “new” old assets added to the MaintainX.

The issue I keep running into is the changing taxonomy of assets already in the database, and how to go about fixing it.