Importing from any of 86 third-party eLogs (Log10Pro, ForeFlight, MCC, LogbookPro, etc).
Yes! Getting your data from other eLogs into Safelog is fast and easy.
- We offer a spectacularly good transition service to help you get your data into Safelog.
- We have carefully reverse-engineered the data formats of over 86 third party eLog formats (see the list below) and have figured out how to get your data from them into Safelog.
- The system has worked well for thousands and thousands of pilots who have come to us from overpromising, underdelivering, overexpensive, or left behind third party logbooks.
- We now feature both a fully-automated self-service transition system which our users, including demo users, are free to use as often as they like, without restriction and our older semi-automated system which, in the unlikely event the fully automated system does not do the trick, can be used by subscribed users under the terms and conditions listed. The fully automated system is incredibly good.
- The new fully automated system is probably all you need. To see it, go to SafelogWeb.com, click Import/Export, then select Automatic Transition. For a complete rundown of the terms and conditions of the semi-automated transition process, log in (a demo account is fine) to www.SafelogWeb.com and then select Import/Export ... Third Party. This will also guide to as to what files we require from you in order to process your specific transition using either system.
- For either system, once you have provided us the requested data files for your chosen format (in most cases this is the third party eLog's data file or CSV output created by the third party eLog), our historical success rate has basically been 100%.
- You may see other eLogs offering some sort of transition service. Typically, they will at most import your basic log data only. Our service here is far more sophisticated, which results in a smoother transition for you. Our transition tools for common third party logbook formats such as Log10Pro, LogbookPro, ForeFlight, MCC, and many others can not only transition your core logbook data, but also things such as your aircraft, aircraft types, airports, contacts, and much more (specifics vary slightly based on what each third party eLog provides). It's hard to fully appreciate this since from your standpoint it's just something that happens in a few moments after you upload your files, but our automated transition service is a true wonder of intelligent software engineering. No other eLog has anything even remotely close.
- We also import from dozens of airline and corporate scheduling / rostering systems (AIMS, FLICA, SABRE, CrewTrac, Merlot, and many more). Please go to www.SafelogWeb.com ... Import/Export or elsewhere in this knowledgebase to learn more about this.
- What are the 86 third party eLogs that you support transition from?
Here is a list of third party eLogbook formats that we can transition your data from. Many but not all of these are supported by the fully automated system, though certainly the most modern and popular ones are as every eLog that somebody has brought to us within the last few years is definitely supported by the fully automated system. This list is always expanding. If you don't see your particular eLog in the list below, please contact our helpdesk and we can discuss adding it.
- AAirLog (American Airlines, Envoy)
- AeroLOG – FlightAce
- AeroLog Pro (Polaris Microsystems)
- AIMS eCrew
- Aircrew Logbook by Andersson Digital Design
- AirLog by AirLogSoftware/LLTSoftware
- AirLog Plus – StanWare
- Aloft Pilot Logbook
- ARINC / ARINCDirect / FOS (Rockwell Collins)
- AvConnect (AvConnect.net)
- AviatorSoft eLogbook
- AvLog / AvLog Pro
- BidWiz – Steve Buzdygan
- CAE TALON / ETA
- CAMP Flight Scheduling System
- Captain's Keeper by Nimblefeet
- Captain's Log 2000
- Cathay Pacific Logbook
- Champagne Services Pilot Logbook
- Cirrus Pilot Logbook by Circumpoint
- Cloudy (France)
- Command Logbook (Australia)
- CrewLog / Flugbuch / FlightTime.Aero / FlightTime.at (Germany/Austria)
- CrewLounge (ex-MCC)
- EASA-Logbook(DOT)EU online Logbook
- EasyLogbook by Aviation Direct
- Electronic Pilot Logbook (MS-Access by e-PilotWorld)
- eLog – cppcentral.de
- eLog / eLogbook 61 - (ARMS - South Africa)
- eLogSite (AAG / American Airlines / Envoy)
- ETA / ETA Pro / Talon (For CAE, etc)
- Flight Log HD by Finkelsoft
- FlightLevel / FlightLevel 2000
- FlightLog / FlightLogHD (Warbred Studios)
- Fly & Go (Fly and Go)
- FlyLogio – Breele
- FOS / ARINCDirect by Rockwell Collins
- JAA-Logbook(DOT)EU online Logbook
- Jeppesen FlightLog / FliteLog / MentorPlus
- Logbook Pro
- Logbook2 (Flightware)
- LogTen Pro
- myControl .aero
- MyLog (Airborne Software International)
- MyOnlineLogbook (Jettsoft)
- Naval Aviator
- OffBlock (Germany)
- OSM Aviation Academy Sweden - PRS (OSM PRS)
- PC Aviator
- PFL Pilots Flight Log (TSE Digital)
- PilotLog (MJICCS Software)
- PilotsPal (UK)
- SkyLog / SkyLog Pro
- Talon / ETA / ETA Pro
- US Army Helicopter Pilot Log (CAFRS) (Form 759)
- US Army Helicopter Pilot Log (CSV) (Form 759)
- US Army Log (iPhone/iPad App)
- US Coast Guard ALMIS
- US Navy / USMC TIMS
- Visual FLT Scheme – Bonds
- What file(s) will I have to send to you to get my data into Safelog?
If your old eLog is in the list above, log in at SafelogWeb.com then click Import/export .. third party .. and then select your old eLog from the list. You can even check this with a Safelog demo/trial account.
Once you do this, you'll be able to see exactly what files we will require from you for your particular old eLog and this will also in many cases provide step-by-step instructions on where
and how to get the files. In some cases, we support multiple formats of third party eLog data, including if you only happen to have access to a mobile or older version.
Going to SafelogWeb.com .. Import / Export .. Third Party will give you far more detail about individual third party eLog formats than we can provide here. However, here's a quick / simplified
summary for some more popular eLogs. We have transitioned hundreds if not thousands of users from each of these: We have had a 100% success rate when users provide us with these. Our transition process for all logbooks is very good, but it's particularly smooth sailing for former users of all the following:
- Log10Pro: Basically, we need your Log10 core data file. This is typically a SQL file but in some cases it may be differently named. We can also work from a number of older and "mobile only" Log10 formats.
- LogbookPro: We need your data .lbk file. Other formats are possible in theory, though pretty much every LogbookPro user as of this writing has been able to provide this.
- MCC / CrewLounge: We need your core data file, unencrypted. We can transition both older "MCC logbook" data and newer "CrewLounge" branded eLogs. We can also work from MCC and CrewLounge exported CSV and XML files.
- Foreflight: exported eLog file. Usually XML format.
- All other third party eLogs: please check the page in SafelogWeb.com referenced above.
- Will you transition all of my data from the third party eLog?
Our goal is to first and foremost transition your basic log data. This often entails also bringing across things such as your aircraft list and crewmember/people list as a matter of course. For things deeper than this, it depends on the
third party eLog type. For some more popular ones, we are able to get more data out. However, in general, please plan that you may have to re-enter some incidental data, such as for example, medical certificate expiration.
- What data do you send back to me?
(This answer applies to the semi-automated process only, which now most of you reading this will not need. Instead, most of you reading this can take advantage of the fully automated system which will silently import your aircraft right into your eLog and curate your data so that it's ready to be matched directly to your Safelog fields).
We take your third party eLog data and then standardize it into a form that can be easily imported via SafelogWeb's CSV importer tool. You are guided step by step as to how to do this
and there is even a help video available. The key step is the 'matching stage.' That's where you'll match fields in the CSV file that we send you with fields in Safelog as you have it configured.
Much of this will be automated - Safelog can normally figure out most field matching on its own. However, the matching stage is where you can tweak the process and also perhaps have a re-think
about what data you want to keep and where. For most people, the import takes at most about 15 minutes.
- Will my totals be the same as in my old logbook?
For most pilots, the answer is a definite yes - your totals will normally be the same in Safelog as they were in your old logbook. Infrequent exceptions to this include where Safelog may correct issues in your old eLog data, where
there are rounding effects due to the intermixing of decimal and hh:mm data, or similar issues. Such exceptions tend to be both rare and minor.
- What if what you send back to me needs further tweaking?
Reverse-engineering third party eLog data is hard. We usually get it right, but sometimes you may find that due to a versioning or other issue, things are not as you'd like them. We'll work with you, within the terms
of the transition program, and do what it takes to make you happy. Please note that this usually requires that you communicate your concerns to us promptly (within 2 weeks) as after that your transition will be considered closed.
If something isn't so, just communicate it to us politely and promptly and let's work together to get your data transitioned over smoothly. Of course, if your old eLog data was messy or had errors, these will generally carry
through into what we do (though the system will detect and fix what it reasonably can automatically).
- Can you transition my data while I am in demo mode?
For formats that are handled by the fully-automated process, which statistically applies to most people readin this, the answer is yes, 100%! go and try it now at SafelogWeb.com .. Import/Export .. Automatic Transition. For the semi-automated process, as this is a labor intensive process, this service is only available to subscribed Safelog users and then subject to the terms found in safelogweb.com ... import/export ... third party. While our success rate
for users who have provided us with the files that we need for given third party eLogs has been basically 100%, out of an overabundance of caution and prudential management of expectations we bill this as a best effort service only. Safelog subscriptions are non-refundable and we do not
offer terms contingent upon the success or failure of transition. Again, our success rate has been basically 100% for people who provide us with the file(s) we ask for which has been the overwhelming majority of users.
Do you represent a 3rd party eLogbook whose best days seem to be behind it?. If so, please contact our helpdesk to inquire
about our "Smooth Landings" program. We can quite likely come up with a win-win-win solution: for your userbase (who enjoy a nearly seamless transition to Safelog), for you and your peace of mind, and for the Safelog community as our userbase grows. We have in the past worked with several other third
party eLogs and the results have been very satisfying for all involved.