Are you a current nShift customer and going to migrate to a Business Central solution built by an nShift partner (e.g. Idyn)? Or maybe you are a partner seeking to initiate the migration process for our mutual customer.
This article will describe how to initiate the migration process needed if the customer is currently using an On-premises solution and must migrate to a Shipment Server API v2 solution.
Initiate the migration:
Submit a request to Ship Customer Service and write in the description that you are migrating to a BC solution and need Shipment Server API V2. If you are the partner making the request on behalf of the customer, we need the contact details of the customer.
nShift Customer Service will now estimate how many hours are needed to carry out the following actions.
- Migrate from On-premises to Shipment Server.
- Migrate all of the carriers and configurations.
- Support testing the solution and go live.
The number of hours needed depends on the complexity of the solution, the number of carriers, services etc.
Setting up the integration
For the BC system to interact with nShift Ship, the following credentials are needed:
- Actor ID(s)
- Client ID
- Client Secret
Once the configuration has been made, the partner can use an API request (GETproducts) to get all product details and finish the integration in the BC solution.
Read more about Shipment Server here.