Tugboat
Mapping Portal — sign in with a one-time code
We sent a 6-digit code to . Enter it below.
PREVIEW MODE — no session. Views show the live option-set (or a placeholder when the API isn't reachable).
Tugboat · Mapping Portal
—
Loading option-set…
Your review queue

Job status

Each job is a source-to-object load you pre-map. Tugboat builds the joins, WHEREs, and final mapping from what you submit.

SeqJobTarget objectOperationStatus
Pre-mapping (you propose intent — Tugboat compiles)
● — → — ⚠ re-scopes fields
Discovery run — · all objects & fields are discovery-sourced — free text only in Intent.
Job scope & record filter
Job scope
Record filter free text · Tugboat compiles the WHERE
Will this load cleanly? ⚠ — — validation rules ▾ —
Source fieldTypeTarget field ParametersMigrateStatus
This is pre-mapping. You propose field intent; Tugboat's team builds the joins & WHEREs and the final tb_fieldmapping from it. Submit syncs your intents back to a Tugboat review lane — it re-validates against discovery_runid before anything lands.
Reports · published from Tugboat

Reports

Read-only. Tugboat publishes these straight into the portal — nothing to download, email, or open as a file.

Published from Tugboat · run — · read-only — refreshed on the next Tugboat publish
—
Articles validated
—
Passing
—
Failing
JobTargetTitlePublish statusImagesLinksReasonsStatus
Run status · published from Tugboat

Job run status

How your loads actually ran — times, row counts, and any issues. Published from Tugboat's Loading Dock; read-only, sorted by sequence.

—
Jobs run
—
Clean
—
With issues
—
Failed
—
Rows loaded
—
Last run
Job IDJobSourceTargetOperationSuccessFailDurationRun dateExecuted byStatus
Client input · user mapping

User mapping

Match each legacy user to a Salesforce user so records keep the right owner and history. Unmapped users fall back to the default migration user.

—
Legacy users
—
Mapped
—
Unmapped
Legacy userRecordsSalesforce userStatus
Client input · state / country

State & country mapping

Map the legacy state/country values discovery found to Salesforce's standard picklist. Unmapped values are rejected on load when State & Country Picklists are enforced.

—
Distinct combos
—
Mapped
—
Unmapped
Legacy stateLegacy countryCountSalesforce standardStatus
Client input · dedupe sign-off

Duplicate sign-off

Tugboat found these likely duplicates. Pick the record that survives (the master), then approve — the others merge into it. Nothing merges without your sign-off.

3
Duplicate groups
1
Approved
2
Pending
7
Records affected
⚠ — —
fieldtop 50
Sample values — data egress to the portal (ADR-0038 / #1026).
ValueMap

New value map

Source value (discovered)Target — StageName picklist
Active×
Lapsed×
Pending×
Comp'd ⚠×
Source values are what discovery found. Targets constrained to the SF picklist. Unmapped values block submit.
Scope

Request a join

Tugboat's team builds the actual join + WHERE from your description and adds this object to the job scope. Its fields become mappable once built — you'll see it as "pending" until then.
Job

Create a new job

Creates a new pre-mapping job (source → target). Tugboat builds the joins & WHEREs from what you map. Saving back to Tugboat is wired server-side — this session previews the flow.
Validation

Field mapping validation