I second what Andrew & Michael say re: Jaspersoft. I can't imagine going straight to Jaspersoft from Business Objects as a part of a 13 to 14 upgrade (don't get me wrong - technically possible - just more than I would care to bite off with the upgrade). I recommend sticking the landing on 14.3, running both reporting technologies in tandem as you work to get Jasper and the Datawarehouse stabilized (our load datawarehouse incremental job is failing again <sigh>). Once stood up, run a separate Jaspersoft project to roll out, train, support, convert reports, etc (ours starts soon). Like Martti mentions, the Datawarehouse and Jasper are a big expansion of the app's footprint by the time you consider dev, test & prod environments.
T-shirt sizing - our historical data shows our 13.2 to 14.3 upgrade 150% the effort & 333% the duration of 13 to 13.2. We virtualized MSSQL while moving from 2K8 to 2K12 and ran into performance issues that took unbudgeted time & effort to resolve. Going directly to 14.3 with the 14.3 installer did not work for us. We had to step through 14.2 then upgrade to 14.3. Notice the CLRTs in the attached document. Step 76 is rebuilding all our scheduled Execute a Process jobs that got cancelled because of a new "Allow only one running instance" feature on the Execute a Process job.
Nice addition - not a fun surprise late in testing to find 50 some jobs aren't running only to find them mysteriously cancelled. I don't know if this is documented now - I never found it at the time we hit it.
In good news - Content Packager was a shining star. Being able to migrate views forward saved 80 to 100 hours of effort from previous upgrades.
HTH