Quote:
Originally Posted by
stomp
Hi Neo,
I assume nobody ever will do a migration/upgrade of a software like the vBulletin used at unix.com for a fixed price. That's beause I assume vBulletin here is absolutely heavily customized, to get really advanced and unique features, so the chances that the upgrade scripts will fail are very high. But I'm not sure for that.
That's the cost of customizations:
- Customizations may interfere with upgrade procedures
- Customized functionality may not work after an upgrade, and need to be fixed and maybe integrated in other ways.
So maybe to just customize the vb-importer of discourse is the best way to go. But hey - if someone says he/she can upgrade the current installation for a relatively small price, why not give a try....
No one can help us (for a reasonable price with top results)....... it is best I do it myself....
and if I pay someone to help, they will encounter the same issues... and it will just be a bigger mess that it is now...
This I am sure 1000%.
I have a lot of experience hiring "experts" and almost every time, it is a waste of both time and money and the end product is far from perfect. I always end up teaching the "experts" how to do the job I am paying them to do, every time.
Let me worry about these things, I'm not seeking advise on approach (but thanks anyway) ..... The work is work and it takes hard work to do it. Don't discount my hard expert work
as if someone else can "cheaply do it".
I assure you that is not the case. Yes, it can be done, but it will look bad. I am working on very small details all not covered by any "migration script".
Thanks.
PS: How many vB3 to Discourse migrations in a Docker container running Discourse have you done so far?