Each job is a source-to-object load you pre-map. Tugboat builds the joins, WHEREs, and final mapping from what you submit.
| Seq | Job | Source | Target object | Operation | Status | Enabled |
|---|
| Source field | Type | Target field | Parameters | Migrate | Status |
|---|
Read-only. Tugboat publishes these straight into the portal.
| Job | Target | Title | Publish status | Images | Links | Reasons | Status |
|---|
See exactly what's different between two of your orgs — structure, permissions, and what changed since the last run.
Every value map in this client's mappings, with its source→target pairs and where it's used. Editing happens per field in the Mapping grid — open a field's parameters and choose “Edit map…”.
How your loads actually ran — times, row counts, and any issues. Published from Tugboat's Loading Dock; read-only, sorted by sequence.
| Job ID | Job | Source | Target | Operation | Success | Fail | Duration | Run date | Executed by | Status |
|---|
What Tugboat discovered — objects, fields, tables, columns, types, and counts. Read-only; no run controls (discovery runs happen inside Tugboat).
Scrub between two retained discovery runs to see objects, fields, and picklist values added, removed, or changed.
Each source Profile maps to a target Salesforce Profile so migrated users land on the right permissions. Read-only mirror of Tugboat — managed there for now.
| Source Profile | Target Profile | Status | Source |
|---|
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 user | Source | SF username | Profile | Active | Migrate |
|---|
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.
| Legacy state | Legacy country | Count | Salesforce standard | Status |
|---|
| Legacy state | Legacy country | Salesforce state | Salesforce country | Status |
|---|
Tugboat found these likely duplicates. For each conflicting field, pick which record's value is correct, confirm the surviving record, then sign off — the others merge into it. Nothing merges without your sign-off.
Something look wrong — a bad value, a missing field, a mapping that won't work? Raise it here. Click any row to open it: the team triages issues in place and everything auto-saves.
| Object | Title | Description | Category | Priority | Severity | Raised | Status | Resolved |
|---|
Every field mapping across all jobs, grouped by target object — search across all of them at once.
Every mapping submission from every SME on this client, straight from the submit — no Tugboat publish required. This is a "recent submissions" feed, not an applied-vs-pending status: a submission here may have already been reviewed and applied by Tugboat.
| Pending submission |
|---|
Every mapping submission from every SME on this client — full history, not just pending. Filter by submitter, job, field, or mapping type.
| Submitter | Job | Legacy field | SF field | Type | Migrate | Submitted | Status |
|---|
| Source value (discovered) | Target value |
|---|