You should just try to export the set up FM simulation via "File->Export->Alembic". Then set your desired frame range and while exporting, the FM simulation is being run in the background and the mesh is dumped out once per frame. That's why the resulting .abc file becomes rather big, 145 MB in this case. And note you will have to re-map the materials manually... only the material assignments are exported / imported, but the values of the material settings AFAIK not (they differ between different programs, this might be the reason.)
I have set up an example blend with a tree fracture scene, derived from your initial blend. In blender you should just need to export this to Alembic. But in case you also want to edit something, it becomes much more tricky IMHO.
You could also convert to keyframed objects, but this will mess up the "fixed" normals again (only FM supports this).
Edit: I did not use fixed normals here, because they work better with more regularly divided base geometry, and best with autohide / automerge. But when the simulation runs and the mesh gets hit, you might get temporary artifacts at the splinters. Instead i tried to mimic the behavior with an Edgesplit modifier. The result is not as smooth as the other approach, but is visually "stable".
Here is the example blend: