Dauntless Aviation
 
FAA Written Test Prep
Checkride Oral Exam Prep
Pilot Logbook Software
Online Pilot Logbook
Aircraft Systems Reviews
JAA Theory Exam Prep
UK PPL/IMC Theory Prep
Aircraft Recognition Tutor
SimPlates IFR Plates
FAR/AIM Reference
More Aviation Software
Aviation Freebies
Free Aircraft Checklists
 
Purchase
Support
Contact
Employment
 
Affiliates and Resellers
 
Home

Safelog Pilot Logbook Software Transition to Safelog Dauntless Aviation

Transition to Safelog

You're not stuck! Now, you can easily transition to the ease of use, power, and flexibility of Safelog from Jeppesen FliteLevel, Logbook Pro, LogTen Pro, ZuluLog, and other less capable or obsolescent logbook systems.

Transition to Safelog

Are you ready to step up to Safelog, the most powerful and flexible Pilot Logbook system? Great!

"I just wanted to thank you for this amazing system, Safelog. I had been using [competitor's product], which now seems antiquated, clunky, awkward and featureless ... I'm a pilot for American Eagle (a new one, at that- less than 50 hours) ... I had no idea logging EVERYTHING I want to log could be SO easy! I'm also blown away that you staff real people to look at my old [competitor's logbook] file in the process of importing it. Thank you, thank you! Your service is worth every penny, and that means a lot coming from someone on first year FO salary!"
- JVC, F/O, American Eagle

Both the PC and web versions of Safelog feature very powerful CSV import tools, allowing you to import neutrally-formatted logbook data from other programs when you transition to Safelog. Hundreds of people have used it when transitioning into Safelog. Click here for a step-by-step guide to importing a CSV file yourself. You should take this route as well if you are starting from a home-made logbook done in Microsoft Excel™, Access™, or any other similar system that can itself export to CSV.

Still, because other logbook systems had a vested interest in keeping your data under their thumb, they often made it difficult for you to get this data into this neutral third-party format. That's the bad news.

The good news is that we've reverse-engineered many of the formats of our competitors and now offer a FREE service to help you get your vital logbook easily data into Safelog. This offer is currently open to users of:

  • AeroLog Pro (Polaris Microsystems)
  • AirLog
  • Aloft Pilot Logbook
  • AvLog / AvLog Pro
  • Captain's Keeper
  • Captain's Log 2000
  • Command Logbook (Australia)
  • FlightLevel / FlightLevel 2000
  • FlightTime (FlightTime.Aero / FlightTime.at)
  • JAA-Logbook(DOT)EU online Logbook
  • Jeppesen FlightLog / FliteLog
  • Logbook Pro
  • LogTen Pro
  • mccpilotlog
  • MyLog (Airborne Software International)
  • OwnerLog
  • PC Aviator
  • PFL Pilots Flight Log (TSE Digital)
  • PilotLog (MJICCS Software)
  • PilotPal
  • RosterLog
  • SkyLog / SkyLog Pro
  • ZuluLog

This list will surely grow over time as well. If your logbook is not on the list above, please ask us via our helpdesk and we'll tell you what we can do or look into possibly offering such a service for your format. Even if your logbook software is not in the list above, you can still of course import your data via the CSV import tools; what this web page here is describing is an additional service to make this process easier still.

Here's how it works:

  1. After you purchase Safelog (any of the 'core' versions, including the Mac, PC, or web versions), you will be able to access the Safelog Transition web pages.
  2. There, you will be able to upload your data files from your old logbook program.
  3. At this point, you'll need to give us up to about two weeks or so (in some cases it may take far less, in others a bit more). We will analyze your files and apply a series of tools that we have written internally to extract your data from those third party formats. This is a semi-automated process and there are certain caveats to it (please see the FAQs below for more details). However, in the end, what we hope to be able to supply back to you within about a week is a CSV (comma separated values) format file that that you can then relatively easily import into Safelog (as it will be designed to be as compatible with Safelog natively as we can make it).
  4. Once you get the CSV from us, you can then use the import features of either SafelogWeb or Safelog for PC to bring the data in. This is a rather straightforward process.
  5. At this point your 'old' data is in Safelog and you are good to go.

 

Frequently Asked Questions


Q

Can you guarantee that you will be able to import my data?

A

Basically, our ability to get the data into a neutral format depends on our ability to reverse-engineer other company logbook formats. We have already done this for most of our major competitors formats and for a large number of obsolete logbooks too. However, the reality is that it may be that quite a few of such third-party logbook systems have perhaps purposely made this difficult if not impossible as their means of effectively holding your data hostage (Safelog, by comparison, has always had a neutral-format export feature). Because it's in our interest to have as many people as possible use Safelog, we will try our best to get your data out, but we can't necessarily guarantee this 100%, nor can we necessarily guarantee that we can get 100% of the data of a given logbook. That said, if your logbook product is in the list above, chances are that we'll have good success. In practice, we've been able to help nearly 100% of those who have come to us with third-party logbook data get their data into Safelog. The exceptions have been really obscure cases such as people coming to us with 20+ year old encrypted database formats.

   
Q

Why do you provide the data in CSV format back to me to import myself? Why don't you just provide it in Safelog's native format?

A

What you get back from us is a CSV format that is basically ready to be imported into Safelog. It requires zero technical ability to do this; all you need to do is to follow a step-by-step wizard. The reason that we do things this way is because this allows you to set up your columns in Safelog the way you'd like them and also allows you to specify certain key information about, for example, your aircraft and other pilots that you may fly with, that your old logbook software might not have captured in a useful way. So, there will be a little bit of work on your part once you get the CSV files from us, but rest assured that we've done most of the technical bits as far as getting the data organized for you.

   
Q

Will you be able to make sense of all of my data?

A

Basically, we will provide a CSV file to help you import most or all of your main flight log. Supplementary material such as for example records of medical certificates will not be imported, but those are few and far between enough that you can enter them manually into Safelog if you'd like to. As far as your main log data goes, we can do only as much as we can in a reasonably automated way with the data – often, what we can't do is due to limitations in your old logbook. An example is this: in some logbook systems, the field for 'flight route' was essentially a non-structured field. We've seen one pilot use this field for anything and everything – sometimes it was his IFR routing, another time it was an actual list of stopped at airports, and so forth. In such cases, for example, due to the fact that the prior logbook didn't enforce structure, we can't necessarily impose it – there's little to be done here if you want to get the data into some structured set other than going through one by one. That's the bad news - the good news is that such examples are few and far between and most people who are familiar with tools such as Microsoft Excel should be able to, with a bit of patience, get things as they want to in the CSV file that we send back before you import them.

   
Q

Will I be able to have my columns set up just like in my old logbook product?

A

Almost certainly YES, you will. In most cases, this is a simple matter of setting up the columns as you will have had them set up in the old product and then importing your data to match. Safelog is very powerful and flexible in this regard, and also can be made to match many common printed logbook formats completely. That said, in some cases there may be small differences between how your old logbook product did things and how Safelog will do them, but these will tend to be minor and done for good reasons (such as because our way ends up being faster or more efficient).

   
Q

Where should I log my flights while you are working converting my old logbook files?

A

If it's not a huge deal, we suggest simply logging on paper for that week or so. This is probably the easiest thing to do as it keeps things separate and simple during the brief 'transition' phase. Or, you can log it in the Safelog logbook software; though as you will go to import the CSV that we will eventually give you, you will have to be careful to ensure that you do not accidentally erase that week's flights.

   
Q

I am not a Safelog customer, but I want to send you the data files from my old logbook...

A

Sorry, this service is ONLY available to existing licensed (paid, not demo) Safelog users. There are no exceptions to this. This service involves a substantial amount of personalized and difficult work by our staff in whipping your data into shape. If you are not a Safelog user, and would like a neutral CSV format from your log data, we will be happy to do this at prices starting at USD $300. Hint: it's cheaper and simpler if you just become a Safelog user and then take advantage of this service for free. The whole point of this service is to ease transition into Safelog.

   
Q

I am interested, but worry that you might not be able to use my data.

A

Indeed, we might not, but if your old logbook product is in the list above, chances are quite good that we will. Furthermore, if you are really concerned and your logbook is not in the list above, send us a message via our helpdesk. We'll contact you personally and perhaps have a look and give you some idea of what we can do.

   
Q

What files do you require?

A

This varies from product to product. Generally, we require the files that contain your logbook data. We do NOT require (nor do we ask) you to send for example the files belonging to the old program itself. We don't care about the program – we just care about your data.

   
Q

Why 'around two weeks?'

A

This 'around two weeks' figure is a bit of an estimate. First of all, please recognize that this is a semi-automated process and the non-automated parts that we have to do are quite technically demanding for some logbook formats. Real humans have to look at your old logbook and apply a series of tools that we have written go get your data out. This requires a high degree of technical and aviation expertise. If it so happens that we already have a matching set of tools, the process may be as quick as a few hours. Occasionally, you may have a slightly different version of something or other, so a bit of tweaking is required. Also, please recognize that we are normal humans who don't necessarily work at 3am on Sunday mornings and we are occasionally subject to illness and prior commitments. Please see this page to see if there are any staff holidays or training sessions scheduled currently as these may affect the speed at which transitions are processed. At all times, you will be able to see the status of your requests through our online system and you can of course contact us via our helpdesk if you are concerned.

   
Q

So the process is completely simple for me?

A

Most of the now thousands (yes, really) of logbook transitions that we have processed do indeed go smoothly. That is, pilots upload their old files to us, we return CSV files, and then the pilots manage to import the returned CSV into Safelog with about an hour or less of work. Sometimes, however, it takes longer and the process is more involved. This may be due to inconsistencies in your data such as because you have a large number of incorrect airport identifiers or other strange values in your old logbook. Other times, difficulties may arise because of unforseen technical issues involved in getting the data you want out of your old logbook. Should you get a file back from us that doesnt contain the data you want, please communicate with us via our helpdesk in a spirit of patience and mutual cooperation, and we'll do our best to fix whatever issue you have. In some cases, this may result in a bit of communication with you and some back and forth as we 're process' your logbook a few times. Please remember that these conversions can be very difficult for us (as they would be for anybody) at times - we're dealing with reverse engineering highly technical data from undocumented and often obsolete or internally problematic file formats. We learn and improve with each one as it is in our interest to make the process as smooth as possible for each pilot. The point is that we ask all pilots who use this system to be open to the possibility that it might take a bit longer and might require some tweaking and communication to get it right for you, but we will do our best and keep working at it to the best of our ability if you communicate constructively with us and help us to help you. We cannot guarantee that it will be a smooth process for everybody all the time--this is simply a reflection of how difficult such transitions are. However, we can guarantee that we will do our best if you have the patience to work with us in the unlikely event that you experience difficulties. Because of this possibility, we ask that if you are facing something like an interview for which you'd like a printout of your log data from Safelog that you give extra time.

   
Q

Will you break encryption?

A

We're not sure if this is ever an issue, but we consider the possibility that some files that some of you may send us may be encrypted – that is, deliberately made difficult to read. Due to legal, ethical, and security considerations, if your file is indeed encrypted, chances are that we will not be able to create a CSV for you. That said, if you have access to your own logbook data in some program, unless the authors were truly cynical, chances are that you will be able to use some 'export' function in that old software to get your data out in a format that we can indeed process for you. This also said, in extreme cases if your data is encrypted and if you can provide to us reasonable and compelling proof that you are indeed the rightful owner, we may be able to do something with it, though this may entail additional costs.

   
Q

Can I import a CSV file even though I haven't gone through you? What if my old logbook software is not in the list?

A

If your old logbook software is not in the list, try contacting us via our helpdesk first. We may well be able to help you as we are interested in expanding the set of old logbook software that we can indeed import. However, if your logbook software is not on the list and we determine that what you have is so obscure or intractable that we truly can't do anything with it, then you can of course use Safelog's import features once you have made your own CSV file from your data. This is not hard to people who have even passing familiarity with MS Excel and indeed thousands of people have come to Safelog from every manner of past data provider in the past before we started offering this service, and this continues to be very much possible.