A clear path
to your workspace.

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

One vessel under service for one season is a native contact-linked opportunity with namespaced vessel type, make and model label, recorded length in whole feet, engine label, hull ID reference, owner label, recorded season phase, storage location code, storage in and out dates, a season contract reference, yard notes, checklist rows and work order rows. Two seasons for the same boat stay independent, and so do two boats belonging to one owner. Other custom fields are preserved.

A storage location code looks like RACK-B3, YARD-R4, SLIP-12 or BAY-2, and its location kind is derived from the prefix rather than stored, so a code and its kind can never disagree. A code is a label your yard wrote down: the kit holds no yard map, capacity figure, dimensions or occupancy limit, and two vessels recording one code are both listed, because that happens. The season band is a fixed twelve month reading frame, not a schedule the kit maintains, and the recorded phase is always what a person last wrote down. A recorded storage in date needs a recorded code, a recorded out date needs a recorded in date and cannot precede it, and a vessel recorded in the storage phase needs both; commissioning and launch do not, because a boat can arrive in the spring without having wintered with you. Checklist rows belong to the winterization or commissioning list, and the sheet reads whichever list the recorded phase works from. Insights reports how many vessels record a phase that differs from the current month’s phase and how many are recorded in storage past their recorded out date; both are observations that two records disagree, never a claim that work is late, and nothing is corrected automatically. There is no slip or berth management, no parts inventory or supplier catalog, no weather or tide data, no scheduling engine, and no invoicing, payments or owner messaging. A recorded date reserves no lift, bay, slip or technician and creates no calendar entry. Season contract and work order amounts are recorded references, separate from native opportunity value, and totals are grouped by currency and never added across currencies. The pipeline stage stays your CRM’s own: saving a vessel record never moves it, and a native stage change never rewrites a recorded phase.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.