Odometer Glitch

[Guymer]

Here's a problem. I replaced an odometer with 187976 miles on it with one that read 285665 miles on it. I did not know that the aCar app was not backing up the data on this vehicle or that the difference in mileage was causing a verification problem I couldn't get my app to sync and deleted this one vehicle. Now Fuelly and aCar Sync, but I can't import the aCar.csv file that I exported for this vehicle to get it back in. As for the odometer issue, I will create a new vehicle with the mileage since the odometer replacement since its not too many records. I attach two of the records that did not back up but aCar seemed to accept...but then it didn't

[Guymer]

What I ended up doing is creating a new account to import the data file into. On record had a longitude latitude error for some reason, so I screen-shot the record, deleted it, and then recreated the record from what was in the screen shot. Interestingly enough I had to modify the vehicle details to what is apparently the new format. Once done I synced it and then transferred it back to myself. I then start a new vehicle record starting at the new odometer setting. I am assuming this will work correctly from now on.

[Guymer]

Want to add that when I logged into my android aCar, the deleted record was back, so maybe I am totally wrong about the odometer readings being the issue. Thank you Fuelly people for fixing this.