The components needed to upgrade data directly from Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2 are now available for download.
Download the upgrade toolkit from PartnerSource or from CustomerSource.
In order to use the toolkit to upgrade data from Microsoft Dynamics 2009 R2 or Microsoft Dynamics NAV 2009 SP1, you will also need the Microsoft Dynamics NAV 2013 development environment and Microsoft Dynamics NAV 2013 R2.
At the Directions EMEA conference in Vienna and the Directions US conference in Nashville, we said that we have a team that is focusing on the Microsoft Dynamics NAV upgrade story. Going through the big transformation from the classic stack to the new product architecture in Microsoft Dynamics NAV 2009 was not easy and is challenging many customers and partners. So for our team, it is essential that the final outcome of our work is that each upgrade is easier, requires significantly less effort, and that it does not disrupt the daily business for our customers.
In Microsoft Dynamics NAV 2013 R2, we introduced support for converting a Microsoft Dynamics NAV 2013 database so that you can run an application that was created in Microsoft Dynamics NAV 2013 on the Microsoft Dynamics NAV 2013 R2 platform, also known as a technical upgrade.
Note: We strongly recommend that you upgrade the application objects as well so that your solution includes the important application fixes and new functionality that is introduced in Microsoft Dynamics NAV 2013 R2.
Secondly, you can fully automate the data upgrade process using the Windows PowerShell scripts that we included in the Microsoft Dynamics NAV 2013 R2 product media. Historically, this process has been known for its tediousness and high risk of human error when multiple operations had to be executed consecutively in all companies of the database that you were upgrading. The scripts automate this work so that you can test and execute your data upgrades more reliably.
Now with this delivery, we introduce an upgrade toolkit for upgrading the data from Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2. This significantly simplifies the upgrade process for those of you coming from Microsoft Dynamics NAV 2009 R2 – or Microsoft Dynamics NAV 2009 SP1.
Included in the new upgrade toolkit are all known data upgrade-related application hotfixes that we are aware of, and we also addressed several platform issues that affected the upgrade scenario.
Note: You must download the latest Microsoft Dynamics NAV platform hotfixes before you start using the upgrade toolkit. The required hotfixes for Microsoft Dynamics NAV 2013 are available in the latest hotfix rollup, which you can download from PartnerSource or CustomerSource. For Microsoft Dynamics NAV 2013 R2, you can download the required hotfixes from PartnerSource or CustomerSource.
When you download the new upgrade toolkit from the link above, you can use it to simply your upgrade process. Here are the main steps in upgrading from Microsoft Dynamics NAV 2009 R2 (or Microsoft Dynamics NAV 2009 SP1) by using the new upgrade toolkit.
Before you start, make sure that you use the latest platform binaries for all versions of Microsoft Dynamics NAV in this process. For more information, see the following pages for the latest updates to the versions of Microsoft Dynamics NAV:
Microsoft Dynamics NAV 2009 R2: Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2009 SP1 and Microsoft Dynamics NAV 2009 R2.
Microsoft Dynamics NAV 2013: Released Cumulative Updates for Microsoft Dynamics NAV 2013.
Microsoft Dynamics NAV 2013 R2: Released Cumulative Updates for Microsoft Dynamics NAV 2013 R2.
You can then use the Finsql.exe file to perform the conversion.
Note During this step, Microsoft Dynamics NAV converts all text and code fields to Unicode format by changing their SQL Server data type. This conversion requires more disk space than usual, since both the database and the log file will grow in size considerably. It can also be a lengthy process.
If your Microsoft Dynamics NAV 2009 R2 database is using SQL Server Collation, within the same step the collation will be changed to a suitable Windows collation. This is because Microsoft Dynamics NAV 2013 and higher versions only support Windows Collation. If you converted your database using the RTM version of Microsoft Dynamics NAV 2013, you may be experiencing collation-related issues after this conversion. Therefore it is strongly recommended to use the latest available version of Microsoft Dynamics NAV 2013 development environment to perform this step.
NoteWe strongly recommend that you take a full SQL Server backup at this stage when the database conversion has completed.
Note If you are upgrading a large database, such as a database size of more than 20-25 GB, make sure that you increase the timeout value in the Microsoft Dynamics NAV Server configuration file. In the CustomSettings.config file, the value is defined in the SQL Command Timeout node. The default value is 10 minutes, which is sufficient in the normal day-to-day work. However, during an upgrade that can take several hours depending on the size of the tables, you must increase the timeout period.
ImportantIt is very important that at least all table objects have successfully compiled before you proceed.
NoteWhen you upgrade from one version to another, this typically involves numerous changes in the structure of the Microsoft Dynamics NAV tables (the object metadata). Database synchronization ensures that these changes in the metadata are applied to the corresponding tables in SQL Server. For example, it changes columns dimensions and data types, drops and create indices, drops and creates indexed views (V-SIFT), creates new tables, columns, and so on.
When the number of changes is high, such as comparing Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2, this synchronization can become a lengthy and resource consuming task.
Database synchronization is triggered upon any request to Microsoft Dynamics NAV Server, such as when you start a client or run a windows Powershell cmdlet. Microsoft Dynamics NAV Server checks if metadata has changed since the last synchronization by comparing the content of the Object Metadata and Object Metadata Snapshot system tables. If a change is found, the synchronization procedure is initiated.
Do NOT stop the Microsoft Dynamics NAV Server service at this point since there are high chances that the database synchronization transaction is still running.
Run Microsoft Dynamics NAV 2013 R2 Administration Shell as Administrator. This opens a PowerShell prompt where the Microsoft Dynamics NAV cmdlets are available.
Run the synchronization command against your upgrade database as follows:
Sync-NAVTenant –ServerInstance <MyNAVServerInstance>
Wait until the cmdlet returns control to the Windows PowerShell window.
The database has now been through a data upgrade to Microsoft Dynamics NAV 2013 R2.
The Microsoft Dynamics NAV Service Experience team
-----Blog post updated in May 2014-----
Hi guys, none of the links to partnersource seems to be working.
The link above for the 2013R2 hotfixes is not working. When you select it you receive the following. The 2031 Hotfix link works fine. Thanks
This Page Could Not Be Found
The page you are looking for has moved or no longer exists – or you might have entered an incorrect Web site address (URL). You might find what you are looking for in one of these areas:
Learn more about Microsoft Dynamics Solutions including:
Microsoft Dynamics CRM
Microsoft Dynamics AX
Microsoft Dynamics GP
Microsoft Dynamics NAV
Microsoft Dynamics SL
For current Microsoft Business Solutions customers:
For Microsoft Certified Business Solutions Partners:
Sorry about the confusion! The links to PartnerSource for the hotfixes for Microsoft Dynamics NAV 2012 R2 are not yet active due to an internal delay. They will be available in a couple of days, we hope, and this will be announced on this blog as well.
Meanwhile, the application hotfixes that you need are included in the upgrade toolkit.
The links are now live!
nice blog and information about Upgrade Toolkit for Upgrading Data from Microsoft Dynamics NAV 2009 R2 and Microsoft Dynamics NAV 2009 SP1 to Microsoft Dynamics NAV 2013 R2 and <a href="www.datasparc.com/download.html"> soracle tools </a>.
Any ETA on the upgrade tool for W1 ?
W1 and NO should be available latest 10/12/2013.
Dmitry Chadayev & The Microsoft Dynamics NAV Service Experience team
Not Working Properly for Indian Localization, After upgrading in NAV 2013 R2 it's giving error as below,
The following SQL error was unexpected.
Invalid column name 'Queue Folder Path'.
Invalid column name 'Queue Folder UID'.
Invalid column name 'Storage Folder Path'.
Invalid column name 'Storage Folder UID'.
Invalid column name 'Autodiscovery E-Mail Address'.
Invalid column name 'Email Batch Size'.
Statement(s) could not be prepared.
And as I checked in both SQL, and development environment, the fields are there.
Hi, I got the following Error executing the Page 104002 on Upgrade601701 with Build 7.1.35701.0, could you help me?
Microsoft Dynamics NAV
Fehler beim Kompilieren von Assembly 'C:\ProgramData\Microsoft\Microsoft Dynamics NAV\71\Server\MicrosoftDynamicsNavServer$NAVISRV2013R2\assembly\Record104002_85.dll'. Dies kann auf Unterschiede zwischen Binärdateien in der Installation oder der Datenbank zurückzuführen sein. Stellen Sie sicher, dass alle Installationskomponenten konsistent und auf dem neuesten Stand sind. Fehlerdetails: 'c:\ProgramData\Microsoft\Microsoft Dynamics NAV\71\Server\MicrosoftDynamicsNavServer$NAVISRV2013R2\source\Record\Record104002.cs(16,54) : error CS1729: 'Microsoft.Dynamics.Nav.Runtime.NavTextConstant' does not contain a constructor that takes 5 arguments
@Thomas: Did you restart the middle-tier?
@Sebastiaan: Yes I did.
Now it works, I have restarted the Service directly.
If I restart (or stop and start) via Admintool it doesn't works.
I think the Administration Tool must be closed while restarting the services, if the Tool isn't closed it didn't restart the whole process?!
Hi Uday Mer,
We've seen this issue before. It should not appear if you compile the system tables immediately after the second database conversion (as instructed in step 7b), before connecting the NST to the database. Once the system tables are compiled, you can connect the NAV Server to the database (or restart the server if it was already pointing to the database) and proceed.
Hope this will help you.
The Microsoft Dynamics NAV Service Experience Team
In step 9b I could not import the table objects because of this kind of errors:
The operation could not complete because a record in the ... table was locked by another user. Please retry the activity.
With trial and error could import it if I compile 100 tables (doesn't matter if it gives error about not existing codeunit, forms, etc.) and then import 100 new table objects. And so on..
I get this error when i run the upgrade tool from 6 to 7.1 on some companies
does anyone have any how to fix that ?
A call to System.Data.SqlClient.SqlCommand.ExecuteNonQuery failed with this message: Column name 'DimVal1' does not exist in the target table or view.