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 unit visit is a native contact-linked opportunity with a namespaced unit type, year and make label, unit length in feet, VIN reference, owner label, bay, arrival date, promised date, released date, a fixed six-key inspection checklist where each item holds a done flag, a date and findings, work orders with stable IDs carrying a status, technician label, warranty flag, claim reference and amount, an optional visit total and notes. The same coach coming back in October is a second visit and a second opportunity, and other custom fields are preserved.

A bay assignment, an arrival date and a promised date are decisions somebody typed. They allocate nothing, reserve nothing, create no native Calendar appointment, send no confirmation and prevent no double-booking; there is no scheduling engine or bay optimization. A block’s length is the recorded arrival day through the recorded promised day inclusive and nothing else. The inspection checklist is six items a technician ticked and dated, not a safety inspection, a roadworthiness certificate or a moisture survey, and an unticked item means nobody recorded it. A warranty flag and a claim reference are words somebody typed, with no manufacturer portal integration, claim filing, authorization lookup or payment. A work order records a label and a status; the kit holds no stock, part number or purchase order. The VIN reference, year and make label and length are staff-entered references, with no VIN decoder or vehicle data service. Overdue means a passed recorded promised date with no recorded release, and a released date requires every work order recorded as done. Recorded amounts are references, separate from native opportunity value, invoices and payments. Empty values read as words, never a dash.

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.