Moving port clearance onto a stronger foundation
Navigator Port is moving forward
From Classic to a cloud-ready platform
Port clearance is changing. Customers need a platform that can grow with new digital requirements. This includes stronger data flow, clearer user management, and more integration options.
That is why we are upgrading Navigator Port beyond its Classic foundation. The upgrade process will be handled carefully, customer by customer, based on the workflows each customer depends on.
Port clearance is no longer just about forms
When Navigator Port Classic was first built, port clearance was largely a vessel-side task: prepare the forms, submit them to the port, and receive clearance.
Today, the reality is different.
Port clearance has become part of a wider operational and compliance workflow. This is one of the main reasons why Navigator Port needs a stronger platform foundation for what comes next.
Port clearance doesn't stop at the gangway
Port clearance information is increasingly needed beyond the vessel, including shore teams, compliance roles and reporting workflows.
Evolving regulatory processes
Authorities and port communities are moving towards structured digital processes and data-based submissions.
Connected operational workflows
Customers expect port clearance to work in sync with their operational environment through integrations with crewing and certificate systems, as well as fleet-level visibility.
How Port Clearance is evolving
Across all three of these shifts, the direction is the same: port clearance is evolving from a fragmented paper trail into a streamlined digital compliance process. It is laying the groundwork for broader operational connectivity. We see this shift in customer expectations, in emerging digital port processes, and in collaborations like the Digital Corridor Project of the MPA Singapore and Port of Rotterdam. Port clearance will increasingly depend on reliable data flows between vessels, shore teams, authorities, and the platforms connecting them.
It sits at the heart of where ship-shore operational connectivity is heading.
Your upgrade route depends on the workflows & modules you use.
Not every customer uses Navigator Port in the same way. The upgrade, including the migration of data, will be planned around workflow readiness, operational dependencies, and customer setup.
Customers using core Port Clearance workflows may be ready to move earlier. Customers depending on Work & Rest, Shore App or other specialist workflows and interfaces may follow a separate route once the required setup is ready.
Before any upgrade path is confirmed, CFARER will review the customer’s current setup and clarify the best next step.
Route 1: Ready to move now
For customers using core Port Clearance workflows with no major dependencies.
Route 2: Prepare special interfaces and workflows
For customers who need Integrations, IT preparation or workflow clarification before upgrading.
Route 3: Planned specialist upgrade
For customers using Work & Rest, Shore App or other specialist workflows. This upgrade and the migrations will follow a dedicated plan aligned with workflow readiness and operational requirements.
Meet Linde & her dedicated team
A route covered by experts
I’m Linde van Wulfften Palthe, Chief Transformation Officer and Global Director Digital Port Clearance at CFARER. Together with my international team, I lead the Navigator Port Classic to Cloud upgrade programme.
Our role is to make sure your transition is handled with structure, care and a clear understanding of your daily port clearance operation.
We know Navigator Port customers do not all work the same way. Every fleet has its own setup. So, we do not treat migration as a one-size-fits-all switch. Before defining your upgrade route, we look at your workflows. Navigator Port Classic remains your operational baseline until your Cloud setup is confirmed.
If you have questions about your upgrade path, timeline, or next steps, you can contact the team and me directly.
A controlled route forward
Customers will move when their setup is ready
The move to the modern Navigator Port platform will not happen in one single step for all customers.
Each upgrade path will depend on the customer’s current setup, operational workflows, vessel environment, and readiness to move. Before upgrading starts, CFARER will review the relevant dependencies and clarify the practical next steps with each customer individually.
The aim is simple: maintain reliable port clearance while moving customers towards a stronger platform foundation at the right pace.
The better we understand your setup, the better we can plan your route
Before confirming an upgrade path, we want to understand how you use Navigator Port today and which workflows, systems, or operational constraints matter most to your team.
This helps us prepare the right route, avoid unnecessary disruption, and ensure the upgrade is based on your actual onboard and shore-side needs.
Key information for your upgrade planning
Your current Navigator Port use
Which workflows and modules are used across your vessels today?
Dependencies and integrations
Which integrations, specialist workflows or operational processes should be considered?
Vessel and IT setup
Who should be involved from your IT team, and are there vessel-specific requirements we should know about?
Preferred timing
Are there operational windows, fleet schedules or internal constraints that should guide the migration planning?
Support throughout the upgrade
CFARER guides the process with a clear view of your setup
Before any upgrade or data migration begins, our experts will contact you and review your current Navigator Port setup, relevant workflows, vessel environment, and known dependencies.
This helps us understand which upgrade path fits your operation and what needs to be prepared before activation. Our aim is to make the transition controlled, transparent, and practical for your teams, both on board and ashore.
Navigator Port Classic was built for a different operating reality
Navigator Port Classic has supported port clearance for many customers over many years. It has helped crews manage complex port requirements and keep daily operations moving.
But the environment around port clearance has changed. Customers now need a platform that can support stronger data structures, easier updates, better access control, and more realistic integration paths.
That is why we are moving Navigator Port onto a modern platform foundation. The goal is not to replace what worked overnight. The goal is to create the base for continuous development, better connectivity, and future digital port clearance workflows.
Structured data
SQL-based architecture supports cleaner data handling, improved data quality, and stronger analytical capabilities.
Access and deployment
Role-based access control, browser-based use within the customer environment, and support for remote deployment simplify administration and daily operations.
Operational efficiency
Workflows for the new digital reality and centralised data management help reduce manual effort, leading to more efficient port clearance processes.
Future connectivity
API capabilities provide a stronger foundation for future integrations with port authorities, customer systems, and evolving digital port clearance ecosystems.
Our four upgrade principles
(1) Workflow readiness first
Customers move based on the workflows they use and whether those workflows are ready for migration.
(2) Clear preparation before activation
Upgrading should start with a clear view of customer setup, vessel scope, IT requirements, and relevant dependencies.
(3) No one-size-fits-all rollout
Different customers may follow different routes depending on their operational setup and migration risk.
(4) Guided by CFARER
CFARER will guide the process together with the customer’s team, including Customer Success, Key Account Management and the upgrade programme owner where needed.
FAQ
Want to know more?
Get quick answers to the most common questions about the upgrade from Navigator Port Classic to the new cloud-ready platform.
What is changing and why is this happening now?
Navigator Port has served seafarers reliably for many years, but the environment around port clearance is changing. Ship and shore now need stronger data structures, better access control, clearer integration paths and a platform that can grow with new digital requirements.
Navigator Port’s next generation is built on a modern SQL-based architecture, deployed within your own environment, and designed to support the connected workflows that port clearance increasingly depends on. We are moving customers onto that stronger foundation – carefully, and at the right pace.
When will my vessels be upgraded?
The upgrade will not happen in one single step across all customers. The timing depends on which workflows and modules your vessels use, your technical setup, and operational readiness.
Before any upgrade is planned for your account, CFARER will reach out to review your current setup and clarify the best route forward. Your vessels will not be upgraded without preparation and direct contact from our team first.
Will there be any disruption to operations during the upgrade?
Our aim is to make the transition controlled and practical for your teams on board and ashore. Before the upgrade starts, we will review your vessel environment, relevant workflows and known dependencies to ensure the switch happens at the right moment.
Vessels using core port clearance workflows can typically be upgraded with minimal disruption. For customers with more complex setups – such as Work & Rest or specialist integrations – we will agree a dedicated plan before any upgrade takes place.
What happens to our Classic data after the upgrade - and can it be transferred to Navigator Port Cloud?
After your upgrade is activated, the previous version of Navigator Port will remain available for 45 days. This gives your team time to retrieve historical records and bring across the data you need, at your own pace.
Data migration arrangements vary by setup. We confirm the specifics with you during upgrade preparation, so your team knows exactly what to expect before the switch.
What does the upgrade require from our side?
The upgrade requires a fresh installation on your side, which means involvement from your IT team is essential. Before the upgrade begins, CFARER will review your current setup and provide clear guidance on what needs to be prepared and installed within your vessel and shore environment.
This typically involves:
- Technical compatibility verification by vessel IT teams
- Installation and implementation process
Beyond the technical installation, we ask that the right people are available for an initial setup review – and that you share any operational constraints or timing preferences that should guide your upgrade plan.
For customers with integrations, specialist workflows or specific vessel IT environments, some additional preparation may be needed. We will identify and communicate this clearly well before the upgrade takes place.
Will pricing change as part of the upgrade?
The upgrade itself does not trigger a price increase. That said, we are reviewing module and subscription pricing as part of this program. If current pricing no longer reflects the scope of use, your Key Account Manager will reach out to you individually before any changes take effect.
What are the main improvements in Navigator Port?
Structured data — SQL-based architecture supports cleaner data handling, improved data quality and stronger reporting capabilities.
Access and deployment — Role-based access control, browser-based use within your environment, and support for remote deployment simplify administration for both vessel and shore teams.
Shore connectivity — Port clearance data is accessible to shore teams, compliance roles and reporting workflows – not just the vessel.
Integration foundations — API capabilities provide a stronger base for future connections with port authorities, customer systems and evolving digital port clearance ecosystems.
Continuous development — A modern platform foundation means new features and compliance updates can be delivered faster and more reliably than was possible on Classic.
Faster Weekly Updates – Weekly updates can be released immediately when ready, instead of waiting for batch releases every few weeks
Does Navigator Port still work offline on the new platform?
Yes, the system will continue to work offline. That’s one of the reasons why we call it “cloud-ready”. It will combine the best of both worlds.
A first look at the new platform
See how Navigator Port is moving forward
Contact us
Let’s make sure the next step fits your operation
This page gives an overview of why Navigator Port is moving forward and how we plan to guide the upgrade. Your own setup may include specific workflows, integrations, or operational requirements that deserve a closer conversation.
If you have questions, concerns, or anything we should consider before your upgrade path is planned, please contact us. We will review it with the right CFARER team and follow up with you directly.
