According to the website of FlightLog Analyzer that application can indeed export the flight data in a format readable by Sky Dolly.
I don’t know exactly which format that would be, but an educated guess would be one of the comma-separated values (CSV) formats.
If that is the case then you can easily edit those text-based formats with any spreadsheet or even text editor of your choice, such as Excel, LibreOffice Calc or Visual Studio Code (the later two freely available).
Sky Dolly can read the following CSV flavours:
FlightRadar24:
Example:
Timestamp,UTC,Callsign,Position,Altitude,Speed,Direction
1717520175,2024-06-04T16:56:15Z,29,"-77.000000,-9.634276",43757,0,228
...
Note: the Timestamp is a Unix timestamp, that is the seconds since 1.1.1970 (if I remember correctly); absolute time, in other words.
Sky Dolly “Position and Attitude”:
Timestamp,UTC,Latitude,Longitude,Altitude,Speed,Pitch,Bank,Heading
0,2024-06-04T16:56:15Z,-77.000000,-9.634276,43757,0,75,38,228
...
Note: here the Timestamp simply starts at 0 (relative time) and is milliseconds.
Both CSV flavours are fully self-descriptive 
The price-winning question is of course: how do you intend to complete the lost flight path fragments that FlightLog Analyzer is not able to recover from the MSFS logbook?
But once you figure that out it is pretty easy and straightforward to extend the exported CSV files (either FlightRadar24 or the Sky Dolly „Position and Attitude“ flavour, depending on what you have) with any text editor or spreadsheet app of your choice.
By the way: while Sky Dolly records your (actually flown) waypoints they are „for your information only“: not relevant for replay.
Hope that helps to recover your logs 