Mental Process - Migrating from Wasp Mobile Asset to Snipe IT
-
A few things: This is only a mental process I am not actively looking to complete this process (at this time at least).
- We're on an old version of Mobile Asset, v6 I believe.
- Using SQL Express
- Operating on an outdated Windows Server OS
- I can backup and browse the database
So if I was starting new (and just discarding everything) I'd just setup Snipe IT, add my users and go from there. Obviously this isn't the case.
There are things that I don't want to lose, like transaction history, asset history, employee and user history, custom reports (uses Crystal Reports 11) such as check out agreements, team audit reports, asset audit reporting etc.
There are also things such as consumable tracking. An easy way to enter and track consumables would be golden also.
An easy way to add child assets (to existing or new assets) IE: GPU's in an existing tower.
So anyways, with the needs aside and just as a mental process, has anyone left an existing Asset Management solution (mobile asset) and moved into Snipe IT?
-
Now if I did start new, I'd have the opportunity to address all of the ad-hocly added assets that follow no convention at all.
As well as to have a clean asset system to work with, no assets that are unaccounted for, and nothing else like that.
The downside is it would take a while to complete, and I'd lose a lot of information.
-
Now if I did import the existing database (some how) I'd still have a mess of a database, but I'd have a current OS, and supported application. (even if only with community support).
I'd still have to audit every asset in the database, confirming what is where. Which is like musical chairs here....
Oh, also I'd have to check out everything that is out to someone (if I didn't import) so that would make it a bit more difficult to start new.
-
Although I could just run a report for "everything checked out" and then audit that individually, confirming assets that are out and in use, and then check those items back out. Of course this means our remote office would also have to audit the assets they have in their possession as well, and check out anything that is out to the people that have those items.
In either case (importing or starting new) auditing the assets is required, so I don't see any way to avoid that.
-
The hard part of anything like this is the manual labor to organize shit.
If it was my call, I would spin up a clean new system and using a report form the old system only import the valid assets.
Manually do the f***ed up assets the right way. and then set a migration date.
Kill change access to the old system and use it only for reporting purposes.
-
Trying to migrate 100% history of anything never ends well.
-
@JaredBusch said in Mental Process - Migrating from Wasp Mobile Asset to Snipe IT:
The hard part of anything like this is the manual labor to organize shit.
If it was my call, I would spin up a clean new system and using a report form the old system only import the valid assets.
Manually do the f***ed up assets the right way. and then set a migration date.
Kill change access to the old system and use it only for reporting purposes.
Yeah, that does make the most sense. And the manual labor is the worst part. It always is.
