Summarizing from the comments on the question:
Helium does do the job if the actions are performed correctly:
- Backing up the app on the source device
- on the target device, copy the folder to the exact location to where Helium creates the backups
- on the target device, restore the app.
If step #2 wasn't exactly followed, Helium wouldn't find the backups on the target device.
A comparable approach would be using adb backup (see our ADB tag wiki for details). To use that, you will need to know the package name of the app to deal with (that is e.g. what you find on the playstore URL by the "id" parameter). Then:
- Connect the source device
adb backup -f foobar.ab -apk com.app.foobarxc2xb9
- Disconnect the source device, connect the target device
adb restore foobar.abxc2xb9
Another detail: you can mix the two approaches. Backups created by Helium contain that
*.ab file, which you could pass to
xc2xb9 of course replace
com.app.foobar with the corresponding app name