'job history information' refers to Job Config History Plugin's data?

I refer to the actual build history of the imported job. Currently the job-import plugin only imports the job configuration xml, but there is no option to import the complete job history or at least the number of the next build that should be performed.
We are currently moving some old jobs to a brand new build server. It'd be a big improvement if it was possible for the moved jobs to just continue the old job's history or at least give it the next build number the old job would have used without editing the files manually and having to reload the configuration.
Edit: We had independent Jenkins instances running that were added with increasing demands, but are now moving to a better scalable master-slave setup.

Given that you'd also want or need build logs, artifacts, etc., and for some projects this is easily tens or hundreds of GB of data, this could well be very time consuming, requiring considering things like retries and resuming transfers. (Granted, maybe not for you, but generally speaking.)

Also, since build.xml files aren't exposed like a job's config.xml is, this will require massive changes in the plugin.

Note that some plugins also store data in additional files (Promoted Builds and Subversion come to mind) which would also need to be considered to result in perfect replica. In comparison, it's trivial to just transfer the job folder over (+ Reload Config on the receiving side, delete project on the sending side) to get the same result.

While I'm not a job import plugin dev, I have serious doubts about the feasibility of this.

I don't wanna copy the whole workspace. I was more thinking in terms of build result reports and logs but this also is a massive amount of data for longer running jobs.
At least an option to import the nextBuildNumber would be nice to be able to build the connection between an old job and its copy on a new system.

Not workspace (temporary build data) – archived artifacts. Those are build records just like the log is. Or e.g. old builds' file parameters – all files uploaded as parameters are archived for older builds, and would also need to be transferred. Hundreds of MB per build in some cases.

Of course, just nextBuildNumber should be fairly easy (speaking as someone who's not a dev of the plugin). Workaround until then: Set Next Buildnumber Plugin.

Did not have all this data in mind when opening this issue.

Also didn't find the next build number plugin before. Will use this now as a workaround.