This page will provide more information when you want to migrate from Ship On-premises to Ship Cloud using the Microsoft Dynamics 365 Business Central integration built by idyn (nShift partner). 

This article will describe how to initiate the migration process needed if the customer currently uses an On-premises solution and must migrate to a Ship cloud in combination with Shipment Server API v2.

Are you using:

• On-premises solution: Needs to be investigated by nShift because customization can be in place.
• API v1: This needs to be investigated because there are small differences with API v2 version.
• API v2: No issues are expected, but the following must be considered.

Supported

• Connect with the demo and production environment.
• Retrieve configuration:
  • Carriers
  • Products
  • Services
• Packaging types (Goodstypes)
• Create booking profiles in Business Central where you can connect products to a default carrier and service.
• Easy shipment booking based on the sales order in Business Central.
• You can retrieve carrier rates via an option in Business Central. That way, you can select the best carrier and service based on costs.
• Possibility to have multiple ship locations.
• Handle customs shipments in an easy way. Article information is transferred to Ship. Note that articles need to be set up properly in Business Central.
• ADR (dangerous goods) can be supported in the integration, however requires a special license and extra set-up. More information can be found on the idyn help page as well.
• Ship towards parcel shops (parcel shop ID needs to be available in Business Central)
• Print ZPL or PDF shipping labels directly out of Business Central via the dropzone (print software of nShift)
• Directly store carrier tracking link in Business Central after booking shipment
• Carrier status information will be visible on shipment level in Business Central

Setup Guide idyn Business Central with Ship

Not supported

• Shipping rules, customer always needs to send the carrier and service in the booking message.
• Custom carriers
• Recycle types / Return pallets.
   

Initiate the migration

Contact nShift Sales and let us know that you would like to migrate 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 customer's contact details. 

We will now estimate how many hours are needed to carry out the following actions. 

• Migrate from On-premises to Cloud.
• Migrate all of the carriers and configurations.
• Support testing the solution and going 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 (GetServices) to get all product details and finish the integration in the BC solution. 

Read more about the Ship API here.