Lync 2010 to Lync 2013 Migration Guide


Now that I have the hardware to run a bigger LAB, I thought it’s time to write about upgrading or to use the correct term Migrating from Lync 2010 to Lync 2013.

LAB infrastructure

So for this lab, I have the following deployed:

  • DC01 is the domain controller
  • Lync10-fe01 is Lync 2010 frontend standard edition
  • Lync10-edg01 is Lync 2010 edge server
  • Lync13-fe01 is Lync 2013 frontend standard edition
  • Lync13-edg01 is Lync 2013 Edge server

One note to consider is that after adding your Lync 2013 Frontend to the pool, you must use Lync 2013 tools to manage Lync 2010 and 2013 servers.


Server Updates

Before you can migrate to Lync 2013 you must make sure your Lync 2010 is up to date and all updates are applied to it

Deploy Lync 2013 Pool

So the scenario here is side by side migration, do deploy Lync 2013 pool, migrate pilot users for testing, then after testing period migrate all users and roles to the new pool and decommission of the legacy Lync 2010 infrastructure.

On the Lync 2013 Front end, install Lync 2013 using the same way you do for a clean deployment, use this link to help you with basic installation of Lync 2013.

When you reach the step to define the topology, you need to select the option “Download topology form existing deployment”

  • expand your Lync deployment >> expand “Lync Server 2013”
  • Right click on “Standard Edition” and click on “Nee front End Pool”
  • On “Define the new Front End Pool” page, Click next
  • In “Define Front End Pool FQDN” page, put the name of your Lync 2013 Front end server, in my case its Lync13-fe01.lyncdude.local
  • Click next
  • Continue normally throw the wizard till you get to the “Associate server role with this front end” page
  • Make sure you are not selecting the option, “Enable and edge pool…….”
  • In define the file store page, “use a previously defined file store” location and chose it from the drop down menu
  • Click next
  • Edit the external Lync web URL and click next
  • Click Next
  • When finish publish the topology.
  • Continue using my previous article to finalize installing your Lync 2013 deployment.

Now if all was smooth, which it should be, you should have now Co-existence between Lync 2013 and Lync 2010. next is to configure your Lync 2013 to use Lync 2010 Edge server for external access and federation.

Configure Lync 2013 Front end to use Lync 2010 Edge server

So now to configure your Lync 2013 front end server to use the Lync 2010 Edge server, it’s a very simple configuration.

  • On the server running Lync 2013 front end, start the topology builder and download the current topology.
  • Right click the Lync deployment and select “Edit Prosperities”
  • In left menu select “Federation route”
  • Check the box says “Apply Federation route assignment to all sites” and from the drop down menu select the name of the Lyn 2010 edge server
  • Click ok
  • Expand the Lync deployment, and expand your Lync server 2013 tree.
  • Expand the Standard Edition Front end and right click your Lync 2013 front end server and click on “Edit Properties…”
  • IN left men, select General, and scroll down till you find “Associate Edge pool”, check the box
  • Then from the drop down menu, select the Lync 2010 Edge server
  • Click Ok
  • Now don’t forget to publish the topology .

Once you done with all of the above you can start with testing Lyn functionalities inside and outside your corporate network and don’t forget to update your Lync 2013 front ends.

Next article I’m writing about migrating Lync 2010 edge to Lync 2013.

Author: Lyncdude

A Senior Service Engineer with more than 9 years of experience in Microsoft Exchange and Microsoft Lync Server / Skype for Business. Egyptian guy lives and works in Frankfurt - Germany. what is written in this blog is my own opinion and thoughts, not my employer and does not reflect their opinion

11 thoughts on “Lync 2010 to Lync 2013 Migration Guide”

  1. Hello,

    I ran to this article as I am creating similar scenario, where lync 2010 is being migrated to 2013. However, I have question about the LyncShare, as in this article it is on old server, shouldnt that be migrated on new server too ?

    1. Hi,

      you are right,
      after migrating all the users (with their Meeting data) from Legacy Lync to the new Lync 2013 Pool, you need to do a number of “Post Migration tasks” including migrating any customs application files hosted in your Legacy FileStore
      like Call park custom application music file, Address book number normalization files.

      recommend that you take a backup of the Legacy FileStore before start with the movement.

      this link include all required post migrations tasks you must do

      Kind Regards,

  2. Hi,

    Great article. I have a Lync 2010 Standard server. Need to migrate to 2013 Standard. I would like to clear one doubt before trying it out. Should I do the “Prepare first standard edition server” step in the new 2013 server ?

    1. Hi jijo,
      You need to run the “prepare first standard…” Step on the server that will run as Lync 2013 front end .
      Good luck with the migration 🙂

      Kind Regards,
      Lync Dude

  3. Hi Lyncdude,

    Great article, thanks!
    Only question: at the end of this article, we have a coexistence situation. On what point do I need to point the existing internal DNS records to the new 2013 Front End server? This I miss this step or is this step coming?

    Thanks again,

    1. you can keep the DNS pointing to Lync 2010 or move them to Lync 2013, in the end the traffic of the user will be forwarded to the correct Frontend hosting the user

  4. Hi,

    There is a link in your article for basic installation Lync 2013 is pointing to your old domain,

  5. Thank you for the help Lyncdude, great walkthru and guide!!

    Question – if I proceeded to create a new Topology and was then requested to perform a Co-Existence scenario… do I have to ‘Download Topology’ and basically recreate all of my settings for the Lync 2013 portion in order for this to work? I have already stepped thru 95% of the Lync 2013 deployment, and of course published all settings to the 2013-CMS.

    Is there a clean way to still incorporate the newly setup 2013 environment, as if I were properly starting with ‘Download Topology’ from the 2010 side?

    I have searched around, perhaps I am not sure exactly what I should search for. If you could help me with this, you would be a lifesaver! I can’t see a way around it – if I download the 2010 and re-publish against the 2013 deployment, it seems like I would have to reconfigure everything anyhow.

    Thank you in advance for your help!!


    1. Hi Brian,

      I’m not sure I fully understand your question.

      So you had Lync 2010 and then start migrating to 2013 by adding the new pool to the Lync 2010 topology?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: