Updated March 2026 · Architecture perspective
Maritime operators often ask whether Salesforce is “heavy” for shipboard reality. The better question is whether your data model can survive the handoff between sea and shore without fragmenting. Salesforce is not magic— it is a governed relational store with workflow, APIs, and mobile options— which happens to match how complex fleets already think about accounts, assets, and work.
This article explains how we think about layering maritime semantics onto Salesforce without fighting the platform. It is opinionated based on deployments we have seen succeed and fail.
Model vessels and facilities as first-class accounts
Treat each hull or yard site as an account (or custom object linked to account) with a stable identifier. People, vendors, and contracts then relate predictably. Avoid parallel spreadsheets that re-key MMSI or IMO numbers with inconsistent formatting—you will regret it at integration time.
Prefer fewer objects, richer relationships
Explosion of custom objects feels flexible until every report requires ten joins. Consolidate where domains overlap: inspections, findings, and corrective actions can chain off a single work-management spine instead of three siloed apps stitched with nightly jobs.
Use record types and page layouts to specialize by vessel class rather than cloning entire schemas per program—unless regulatory separation truly demands it.
Integrate at the boundary, not the middle
ERP, maintenance systems, and AIS feeds should push events into Salesforce via platform events or middleware—not dump opaque blobs nobody queries. Define which system is authoritative for each fact (hours run, fuel uplift, crew embarkation) and enforce it in integration contracts.
Mobile and offline reality
Salesforce mobile offline has limits. Design for intermittent sync: batch uploads when alongside, validate conflicts explicitly, and never assume real-time truth at sea for safety-critical decisions without local redundancy where regulation requires it.
Governance your CISO will recognize
MFA, IP login ranges, encryption policies, and Shield where needed—these are table stakes for enterprise maritime. Salesforce gives you the knobs; Shipyard Intel aligns maritime apps to those knobs instead of inventing parallel security models.
Continue with maritime cyber basics and the compliance readiness checklist.
License and cost realism
Platform licenses, API call volumes, and Experience Cloud logins scale with adoption. Budget pilots with headroom for integration bursts (e.g., bulk certificate imports) so you do not throttle production jobs during cutover. Finance should model three years, not three months—maritime programs rarely decommission quickly once crews depend on mobile flows.
Sandbox strategy matters: partial sandboxes may strip related records and break maritime graphs. Full sandboxes cost more but reduce false negatives during UAT—often cheaper than a failed go-live weekend.