Switching from MCC Pilot Log or CrewLounge PilotLog to Wingman: complete migration guide

Pilots who chose MCC Pilot Log or CrewLounge PilotLog had good reasons at the time. Both apps have been around long enough to build genuine user bases, both handle the core job of recording flight time, and both have served pilots through multiple career stages. None of that changes because a different option exists.

What does change, for a growing number of pilots, is what the logbook needs to do. Roster integration, multi-device sync, and clean alignment with DGCA and eGCA workflows have moved from nice-to-have to part of the day-to-day. Pilots flying for IndiGo, Air India, Akasa Air, and SpiceJet are increasingly looking at logbook software the way they look at other operational tools: it should fit the actual workflow, not the other way around.

This guide covers why some pilots switch, what Wingman does that the source apps do not, the export and import process from each source, post-migration verification, and the answers to the questions that come up most often during the transition. None of it requires deleting your old data.

Why pilots migrate from MCC Pilot Log or CrewLounge PilotLog

Both source apps do certain things well. MCC Pilot Log has a long history on Windows and Android, and pilots who set it up years ago are usually familiar with its data model. CrewLounge PilotLog is feature-dense, with a strong following among long-haul crews. Neither app is broken, and most people who switch will say the same thing: the app worked fine, but the workflow around it stopped fitting.

The friction points that come up most often:

• Manual entry remains manual. Both apps support roster import in some form, but the breadth of carrier and roster-system coverage varies. Pilots on systems that are not natively supported end up keying flights by hand after every duty cycle.

• Platform fragmentation. A pilot using one device in the briefing room, another at home, and a third on the road notices when the logbook feels inconsistent across them.

• Regulator-specific workflow. DGCA and eGCA expectations have specific shapes. Indian commercial pilots want totals, recency tracking, and export formats that map cleanly to the regulator they actually file under, without manual reformatting.
  

These are workflow concerns, not feature gaps in isolation. Pilots who hit these constraints often look elsewhere, and when they do, they want a path that does not cost them years of flight history.

What Wingman offers that those apps do not

The product positioning is straightforward, and is worth covering once before returning to the procedural sections.

Same logbook on every device. Wingman runs on iOS, Android, and Web, with the same flight data on each. A flight logged on the phone after landing shows up on the iPad in the next briefing and on the web app at home. There is no separate desktop sync utility.

Automatic roster import. Wingman pulls scheduled flights from AIMS eCrew, NavBlue RAIDO, CAE Crew Access, ARMS, CESAR, Sabre, FLICA, and PDC CrewConnex. For pilots at IndiGo, Air India, Akasa Air, SpiceJet, and similar operations, this typically means manual entry is reserved for edge cases like training flights or ferry sectors, not the routine line.

DGCA and eGCA workflow as a first-class concern. Wingman is built around the regulatory requirements Indian commercial pilots actually file against, including the formats expected when you upload your logbook to eGCA. Other regulators are supported as well: FAA, EASA, UK CAA, GCAA, GACA, NZCAA, HKCAD, CASA, and CAAS.

Wingman is used by more than 30,000 pilots across 400+ airlines. Pricing is ₹4,499 per year for Indian pilots and $59 per year internationally, with a free tier up to 250 hours. The product positioning ends here. The rest of this guide is procedural.

How the migration works, at a glance

Source app (MCC Pilot Log or CrewLounge PilotLog) → Export → CSV file on your device → Upload → Wingman import → Field mapping and review → Verification against source totals → Live in Wingman

If stuck: Assisted migration by Wingman team

The standard export format for both source apps is a CSV file, with some support for the ICAO-compatible logbook CSV. Exact format names and field labels should be checked against your installed app version before you start, since they change between releases.

Step-by-step: export from MCC Pilot Log

The aim of the export step is a single CSV file with your complete flight history: dates, routes, aircraft type, registration, PIC and SIC time, night, instrument, landings, endorsements, and any custom fields you used.

The general flow:

1. Open MCC Pilot Log on the device where your current data lives.

2. Locate the export or backup function. In MCC Pilot Log, this is usually found in the settings or data management section, though the exact menu path varies by app version and platform.

3. Choose CSV as the export format. If your version offers an ICAO-compatible logbook CSV, that is also a valid choice. Wingman's import handles both.

4. Save the exported file to a location you can reach from the device you will use to upload to Wingman: cloud storage, email attachment, or a local folder you can access from your phone or laptop.

5. Make a second copy of the file and keep it as a backup before doing anything else. This is the single most important step in the entire migration.

If your installed version does not show a clear export option, or if you have used MCC Pilot Log across multiple devices and are not sure which has the most complete data, contact the Wingman team. The export step is the one that benefits most from a second pair of eyes, because mistakes at this stage propagate forward.

Step-by-step: export from CrewLounge PilotLog

The same principle applies. The goal is a single CSV file representing your complete flight history.

The general flow:

1. Open CrewLounge PilotLog on the device that holds your primary logbook.

2. Find the export function. CrewLounge PilotLog generally exposes export options in the file or data management area, but the specific label and location depend on which platform and which version you are using.

3. Select CSV as the export format. If you see an ICAO-compatible logbook CSV option, either works for Wingman's import.

4. Save the file to a location accessible from the device you will upload from.

5. Keep a backup copy of the exported file. If anything looks wrong during import, you want the original sitting untouched on a different drive or cloud folder.

Pilots who have multiple flight categories, custom totals fields, or unusual aircraft types should check whether those fields are included in the export. If anything looks missing in the exported CSV, fix it in the source app before you import, not after.

Step-by-step: import into Wingman

Once you have a clean CSV file, the import flow on the Wingman side is the same regardless of where the file came from.

1. Sign in to Wingman on the platform of your choice. The import flow is available on iOS, Android, and the web app.

2. Open the import section from your account settings.

3. Upload the CSV file.

4. Review the field mapping screen. Wingman attempts to match the source columns to its own fields automatically. Where the match is ambiguous, the flow asks you to confirm or remap.

5. Confirm the import. Wingman processes the file and shows a summary of what was imported.

Manual migration support. The Wingman team offers assisted migration for pilots who would rather hand off the import. This is useful if your export file is unusually large, if you have used multiple logbook apps over a career and want them merged, or if a self-service import flagged issues you would rather not troubleshoot.

What to verify after migration

Once the import completes, run a verification pass before you treat Wingman as your primary logbook. The goal is to confirm that your totals in Wingman match your totals in the source app, exactly.

The checklist:

Field	What to check
Total flight hours	Compare the grand total in Wingman against the grand total in the source app, to the minute.
Total landings	Day landings and night landings should both reconcile.
PIC and SIC time	Both should match. Some source apps treat dual or instructor time as separate columns that need explicit mapping.
Night and instrument time	These are commonly miscategorised between apps and should be verified independently.
Aircraft type totals	Each type rating should reconcile separately. If you have flown both A320 and B737, check each.
Endorsements	Type ratings, instrument ratings, line check completions, and other endorsements should all appear.
Currency and recency	Last landing dates, takeoff and landing recency, and licence and medical expiry tracking should all be populated.

If a number does not match, do not edit it manually until you understand why. Mismatches usually trace to a known cause: a field that was not mapped during import, a custom column the export did not include, or a difference in how the two apps round time. The Wingman team can diagnose most discrepancies from the export file itself.

Keep your old app installed and untouched until verification is complete. Treating the source app as a read-only reference for a few weeks removes the time pressure from this step.

What you gain in the switch

Once the migration is complete and the totals reconcile, the workflow shifts in three concrete ways. First, manual entry becomes the exception. Most flights arrive in your logbook through the roster import before you would have entered them manually.

Second, the logbook stops being device-specific. The same data is on the phone, the iPad, and the web app, with the same UI.

Third, regulator workflow stops being a separate task. Exports for DGCA and eGCA are produced from the same data that powers the rest of the app. International regulators are handled the same way.

None of this requires giving up the records you built in the source app. They come with you.

Frequently asked questions

Will I lose any flight data when switching from MCC Pilot Log to Wingman?

The aim of the migration is a complete transfer of every field that was in the source export. Some fields, particularly custom user-defined columns, may need explicit mapping during import, and rare data shapes may need manual intervention. Keep a copy of your source export until you have verified totals.

Can I migrate from CrewLounge PilotLog without starting my logbook from scratch?

Yes. The migration path is a CSV export from CrewLounge PilotLog and an import into Wingman, with field mapping handled during the import. Your flight history, endorsements, and currency entries come across in the same flow.

What file format does Wingman accept for logbook imports?

Wingman imports CSV files. ICAO-compatible logbook CSV is also handled. Field names are mapped during import, so column order in your export does not need to match Wingman's internal schema.

How long does migration take from MCC or CrewLounge?

For a typical commercial pilot with a few thousand hours and a clean export, a self-service import and verification pass takes one or two hours, most of which is the verification step. Larger or more complex histories may take longer.

Does Wingman support manual migration help if I run into problems?

Yes. The Wingman team offers assisted migration. Pilots who would rather hand off the import, or who hit a self-service issue, can contact the team and have the migration handled for them.

After importing, how do I know my totals are correct?

Compare totals in Wingman to the same totals in the source app, item by item: grand total hours, landings, PIC and SIC time, night, instrument, each aircraft type, and endorsements. If anything is off, do not edit manually. The Wingman team can usually diagnose the cause from the source export.

Can I keep my old app running alongside Wingman during the transition?

Yes, and it is recommended for the first few weeks. Treat the source app as a read-only reference, do not log new flights into it, and rely on Wingman as the source of truth. Once verification is complete, you can retire the old app at your own pace.

Ready to make the switch?

You can start your Wingman logbook for free, on the device of your choice, and import your existing records when you are ready. If you would prefer the import done for you, contact the Wingman team and they will handle the migration end to end.

The flights you have already flown stay yours. The workflow around them is what changes.