How to migrate NavSherpa to Business Central Online
Prerequisites
-
Migration is using the
Cloud Migration Setup / Management tool in
Business Central Online, which supports
BC 140 as a minimum version.
-
Your C/AL
NavSherpa must be upgraded at least to the version
NSPW114.00.04.
-
AL Extension
NavSherpa must have at least version
17.07.00,
18.05.00 or
19.00.00, otherwise the
Start Data Upgrade to AL function in
NavSherpa Setup will be missing.
-
AL
NavSherpa requires a different license key than C/AL version. If you are migrating from C/AL BC 140, please order your extension NavSherpa license first.
Data Migration
Regarding NavSherpa there is only one additional step, before you can run the data migration. When you have finished the Cloud Migration Setup, go to Cloud Migration Management and from the menu choose Manage Custom Tables.
Here you need to map NavSherpa C/AL table names to their counterparts in AL. To speed things up, you can use Populate From Extension function and choose the NavSherpa extension.
After that just fill in C/AL table names like into Source Table Name column – see the table below.
Extension Name
|
Table Name
|
Source Table Name
|
NavSherpa
|
NSP SharePoint Site Setup
|
SharePoint Site Setup
|
NavSherpa
|
NSP SharePoint Site Setup Par.
|
SharePoint Site Setup Param
|
NavSherpa
|
NSP SharePoint List Setup
|
SharePoint List Setup
|
NavSherpa
|
NSP SharePoint List Mapping
|
SharePoint List Mapping
|
NavSherpa
|
NSP SharePoint List Workflow
|
SharePoint List Workflow
|
NavSherpa
|
NSP SP WF. Attr. Mapping
|
SharePoint WF Att. Mapping
|
NavSherpa
|
NSP SP List Content Type
|
SharePoint List Content Type
|
NavSherpa
|
NSP SharePoint Table Link
|
SharePoint Table Link
|
NavSherpa
|
NSP SharePoint Synch. Log
|
SharePoint Synchronize Log
|
NavSherpa
|
NSP SharePoint Record Mapping
|
SharePoint Record Mapping
|
NavSherpa
|
NSP SharePoint Doc. Mapping
|
SharePoint Document Mapping
|
NavSherpa
|
NSP SP WorkFlow Mapping
|
SharePoint WorkFlow Mapping
|
NavSherpa
|
NSP SP Content Type Mapping
|
SharePoint Cont. Type Mapping
|
NavSherpa
|
NSP General Buffer
|
NavSherpa General Buffer
|
NavSherpa
|
NSP Access Group
|
NavSherpa Access Group
|
NavSherpa
|
NSP Access Group Member
|
NavSherpa Access Group Member
|
NavSherpa
|
NSP NavSherpa Setup
|
NavSherpa Setup
|
NavSherpa
|
NSP NavSherpa User
|
NavSherpa User
|
NavSherpa
|
NSP Access Group Mapping
|
NavSherpa Access Group Mapping
|
NavSherpa
|
NSP SharePoint Record Navigate
|
SharePoint Record Navigate
|
NavSherpa
|
NSP SharePoint Access Token
|
SharePoint Access Token
|
Now you are ready to run the data migration. If needed, you can create a diagnostic run first – if there are some issues with NavSherpa table mappings, you will see the tables in Tables with Warnings section.
Manual Steps
After you finish the data migration and data upgrade, there are a few manual steps that you need to do to get NavSherpa running in Business Central Online.
Important: Before going live, make sure, that you disabled all automatic jobs in your on-prem Business Central! You certainly do not want two Business Central instances connecting and uploading files to one SharePoint.
New License Key
If you are migrating from Business Central 14 (C/AL version), your NavSherpa license key will not work with AL extension version. Please order the extension license key in advance and after migration enter the correct license key in NavSherpa Setup. Ensure that the license is valid for your VOICE account number.
Authentication
-
If you were using
any other than OAuth authentication, you need switch to it now. Please have a look at the installation tutorial videos or
NavSherpa help and run the
Setup Access Token wizard to set it up.
-
When using
OAuth authentication, you may need to refresh the access token.
-
Please open your root SharePoint site setup and check the connection by selecting the
Author SP Field Internal Name. If you can see the list of fields from SharePoint, your connection is ok and you can proceed to the next step.
Run NavSherpa data upgrade to AL
Go to NavSherpa Setup and run action Start Data Upgrade to AL (run this action in each company, where you have NavSherpa). This will perform the last steps that are needed to update the data to AL version. If something goes wrong, fix the errors and run the action once more.
Note: Without the NavSherpa data upgrade there are some vital information missing in SharePoint List Setup table and your NavSherpa will not work properly.
Start NavSherpa Automatic Job
As the last step,
create or start the job queue entry responsible for
NavSherpa automatic jobs.
Important: Please ensure, that the automatic job in your old database is stopped by now and no users are adding documents there!