Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to migrate from LanScan Pro to LanScan #7

debookee opened this issue May 30, 2018 · 0 comments

How to migrate from LanScan Pro to LanScan #7

debookee opened this issue May 30, 2018 · 0 comments


Copy link

@debookee debookee commented May 30, 2018

Upgrade LanScan Pro v5

  1. Upgrade LanScan Pro to last 5.1.x. (Migration menu doesn't appear in 5.0)
  2. Click on icon "Free upgrade to LanScan In-App" or Help -> Migrate to LanScan In-App
  3. A popup appears with intructions
  4. Read it carefully (follow this advice carefully!)
  5. Copy the token code


Download LanScan v6

  1. Download LanScan v6 from App Store on
  2. In LanScan, go in menu Help -> Migrate from LanScan Pro v5
    (if you don't see the menu, follow this FAQ)
  3. Enter the token & Calculate Token (must be done on the same Mac it was generated)
  4. If token is ok, download link appears with a free purchase -> Purchase


Is migration a success?

At this point, you have all features of LanScan Pro v5: all hostnames and comments are fully displayed.
Verify it by going in Help -> Support -> Show In-App purchases

You should see:

  • isInAppv5FreePurchased:1
  • isInAppv5Purchased:1

Optional $0.99 upgrade for TCP port scanner

LanScan v6 also introduces a new TCP port scanner, which is a paying upgrade of $0.99 for current LanScan Pro users.
This upgrade is optional and is the first paying upgrade since 2011. It’s not scheduled to add other paying upgrade in a near future.

You'll find more informations about TCP port scanner here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant