|
Yes! Moving your pilot logbook from another electronic logbook into Safelog is usually fast and straightforward.
We have put a great deal of care and engineering effort into making the transition to Safelog as smooth as possible. Our transition system has helped thousands of pilots move their historical flight records from other electronic logbooks into Safelog.
We currently support transition from more than 86 third-party electronic logbook formats, with more being added over time.
Our transition tools have been developed by carefully analyzing and supporting the data formats used by a wide range of competing and discontinued electronic logbooks. This allows Safelog to do much more than simply import a basic list of flights.
Depending on the source logbook and the data it makes available, Safelog may also be able to transition information such as:
- Flight records
- Aircraft
- Aircraft types
- Airports
- People and crewmembers
- Contacts
- Other supporting logbook data
The exact information available varies by third-party logbook, but for many of the most popular formats the transition is impressively comprehensive.
Two different transition methods are available.
Safelog now offers a fully automated self-service transition system for many third-party logbooks. This system can be used by Safelog subscribers and even by demo users, and you can try it as often as you like.
In most cases, the fully automated system is all you will need.
To try it:
- Log in at SafelogWeb.com.
- Select Import/Export.
- Select Automatic Transition.
- Choose your existing electronic logbook and follow the instructions.
We also continue to provide our older semi-automated transition process for subscribed Safelog users when needed. This can be useful in the relatively uncommon situation where the fully automated system does not support a particular variation of your source data.
To see the requirements and terms for the semi-automated process, log in at SafelogWeb.com and select Import/Export > Third Party.
Once users provide the required data files in a format we support, our historical success rate has been extremely high, effectively 100% for properly supplied supported files.
In many cases, all you need is the original electronic logbook data file or an export file such as CSV, XML, or another supported format.
Safelog also supports imports from many airline and corporate scheduling and rostering systems, including systems such as AIMS, FLICA, SABRE, CrewTrac, Merlot, and others. See the Import/Export section of SafelogWeb for more information.
-
Which third-party electronic logbooks can Safelog transition from?
-
Safelog currently supports transition from more than 86 third-party electronic logbook formats.
```
Many of the most popular and modern formats are supported directly by the fully automated transition system. The supported list continues to expand as new formats are requested and as other electronic logbooks evolve.
If your current electronic logbook does not appear in the list below, contact our Helpdesk. We may already be able to work with it, or we may be able to add support.
- AAirLog (American Airlines, Envoy)
- AeroLOG – FlightAce
- AeroLog Pro (Polaris Microsystems)
- AeroTrax
- 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
- CapzLog.aero
- Cathay Pacific Logbook
- Champagne Services Pilot Logbook
- Cirrus Pilot Logbook by Circumpoint
- Climb!
- 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)
- ExcelPilotLogbook
- Flight Log HD by Finkelsoft
- FlightAware
- FlightLevel / FlightLevel 2000
- FlightLog / FlightLogHD (Warbred Studios)
- FlightLogg.in
- FltPlan.com
- Fly & Go (Fly and Go)
- FlyLogio – Breele
- Foreflight
- ForPilots
- FOS / ARINCDirect by Rockwell Collins
- FourthStripe
- IntelliPilot
- JAA-Logbook(DOT)EU online Logbook
- Jeppesen FlightLog / FliteLog / MentorPlus
- Lockr.Aero
- Logbook Pro
- Logbook2 (Flightware)
- LogShare
- LogTen Pro
- mccpilotlog
- MilKeep
- myControl .aero
- MyFlightBook
- MyLog (Airborne Software International)
- MyOnlineLogbook (Jettsoft)
- Naval Aviator
- OffBlock (Germany)
- OSM Aviation Academy Sweden - PRS (OSM PRS)
- OwnerLog
- PC Aviator
- PFL Pilots Flight Log (TSE Digital)
- PilotLog (MJICCS Software)
- PilotPal
- PilotPartner
- PilotPro
- PilotsPal (UK)
- RosterLog
- SchedAero
- SkyLinked
- 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
- VortexLog
- Xineo
- ZuluLog
```
-
What file or files do I need to provide?
-
|
The easiest way to find out exactly what we need is to check inside SafelogWeb.
```
Log in at SafelogWeb.com, then select Import/Export > Third Party and choose your old electronic logbook from the list.
You can do this even with a Safelog demo or trial account.
SafelogWeb will tell you exactly which file or files are required for your particular source logbook and, where appropriate, provide instructions explaining how to obtain them.
For some third-party products, we support several different source formats, including exports from older versions or mobile-only installations.
|
|
The information inside SafelogWeb is more detailed and current than anything we could reasonably reproduce here, but the following are some common examples:
-
LogTen Pro: We can generally work from the main LogTen data file, commonly a database file, and we also support a number of older and mobile-oriented formats.
-
Logbook Pro: The normal source is the Logbook Pro .lbk data file.
-
MCC / CrewLounge: We can work with unencrypted core data files as well as a number of CSV and XML exports. Both older MCC Logbook data and newer CrewLounge-branded formats may be supported.
-
ForeFlight: The normal source is the exported electronic logbook file, commonly in XML format.
-
Other electronic logbooks: Check SafelogWeb.com > Import/Export for the current requirements for your specific system.
We have successfully transitioned large numbers of pilots from each of these systems.
```
-
Will Safelog transition all of my data?
-
Our first priority is to transition your core flight logbook data accurately and usefully.
```
In many cases, the process also brings across related information such as your aircraft list, aircraft types, airports, and crewmember or people records.
How much additional information can be transitioned depends on the source logbook and what data it makes available to us. Some popular electronic logbooks provide enough structured information for a particularly comprehensive transition.
You should nevertheless expect that some incidental information may need to be re-entered manually after the transition. Examples might include items such as medical certificate expiration dates or other account-specific information that the source logbook does not export in a usable form.
```
-
What happens in the older semi-automated transition process?
-
Most users today will be better served by our fully automated transition system. However, for source formats that still require the older semi-automated process, we standardize your third-party logbook data into a form that can be imported into Safelog using the SafelogWeb CSV importer.
```
Safelog then guides you through a field-matching process in which source fields are matched with the corresponding fields in your Safelog configuration.
Much of this matching can usually be determined automatically. You still have an opportunity to review the results and adjust how particular information should be handled.
For most pilots, the final import process itself takes only a short time once the prepared transition data is available.
```
-
Will my totals be the same as they were in my old logbook?
-
For most pilots, yes. Your totals should normally agree closely with those in your previous electronic logbook.
```
Rare differences can occur when the original logbook contains inconsistencies, when Safelog interprets or normalizes unusual source data, or because of rounding differences between decimal-hour and hours-and-minutes formats.
Such differences are generally uncommon and minor.
```
-
What if something needs additional adjustment after the transition?
-
Third-party logbook formats can be complicated, and different versions of the same product sometimes store data differently.
```
Our transition systems handle the overwhelming majority of supported data very well, but occasionally a version-specific or source-data issue may require further attention.
If something does not look right, please contact us promptly and explain the issue clearly. For transitions handled through the semi-automated service, concerns should normally be raised within the time period specified in the applicable transition terms, generally within two weeks.
It is also worth remembering that if the original electronic logbook contains errors, inconsistencies, or poorly structured data, some of those issues may naturally carry through into the transition. Safelog will detect and normalize what it reasonably can, but no transition system can reliably infer the intended meaning of every piece of problematic source data.
```
-
Can I try transitioning my data while I am still using Safelog in demo mode?
-
Yes, for formats supported by the fully automated transition system.
```
In fact, we encourage you to try it. Log in at SafelogWeb.com and select Import/Export > Automatic Transition.
The automated transition system can be used by demo users and is an excellent way to see how smoothly your existing electronic logbook data can move into Safelog before you subscribe.
The older semi-automated transition service involves staff time and is therefore available only to subscribed Safelog users, subject to the terms shown in SafelogWeb.com > Import/Export > Third Party.
Although our historical success rate has been extremely high when users provide the required supported source files, the semi-automated transition service is provided on a best-effort basis. Safelog subscriptions are not contingent on the success or failure of a particular third-party transition.
```
Do you represent an electronic logbook whose best days may be behind it?
If you operate or represent a third-party electronic logbook and are considering how best to support your users going forward, please contact our Helpdesk and ask about our "Smooth Landings" program.
We may be able to develop a transition arrangement that benefits everyone involved: your existing users receive a smooth path into Safelog, you gain peace of mind knowing that their historical records can continue to be useful, and the Safelog community welcomes a new group of pilots.
We have worked with other electronic logbook providers on transitions in the past, with very positive results.
|
