Skip to content
Help Center
Submit a request Sign in

Plan and run a TeamSupport import

The TeamSupport importer supports API migration, Excel snapshots supplemented with conversations/files, and a report-only activity path. Previewing scope and mappings before a run helps preserve useful customer context and identify records that need attention.

Applies to: Supportbench Core. Location: Settings → Integrations → Import from TeamSupport. Importing requires Administer all integrations.

Before you begin

  • Confirm your migration authority and identify the exact TeamSupport organization and destination account.
  • Choose the source mode before obtaining credentials or preparing files. API and Excel modes need source API access; report-only mode does not.
  • Prepare representative source records and review customer matching, routing, visibility and existing destination data before a run.

Configure and verify

  1. Open Settings → Integrations → TeamSupport Import and choose the import source.
  2. For API or Excel mode, enter the organization and API token and test the connection. For report-only mode, enter the organization ID without an API token or connection test.
  3. Upload and validate the source file when using Excel or a report. Review the mode-specific confirmations below.
  4. Discover or preview the available fields, set destination defaults and save the intended mappings.
  5. Run a narrow representative sample. Reconcile customer matches, case details, activity visibility and failures before expanding the scope.
  6. To resume, select the saved run and review its state before Continue. Re-enter the token for API/Excel modes when requested.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
Organization ID / API token / Test connectionConnects to the intended TeamSupport organization. The token stays in the server session.Use authorized source credentials and confirm the organization.
Import sourceTeamSupport API; Excel export plus API conversations/files; or CSV activity report without API calls.Choose the source that contains the data you intend to migrate.
Cases / From / ToAll, open or closed cases and the selected date range for supported source modes.Start with a narrow representative scope.
Daily request allowanceSupportbench’s internal daily API request safety ceiling. It is separate from the provider’s own quota or rolling limits.Keep a suitable safety allowance; an override does not bypass provider rate limits or denied requests.
Sample Ticket ID / Discover fields / Preview ticketsInspects representative source data and available fields.Preview varied records before saving mappings.
DefaultsDivision, Issue, Priority, open Status, fallback Queue and fallback/incoming/outgoing/internal activity types.Choose valid destinations before running the import.
MappingsIncluded/optional fields, standard-only, search, entity filters and advanced options.Review every required destination and save the selected mappings.
Run controlsContinue, Pause, new tickets only, update existing and new, Cancel, Retry failed and budget override.Read the current run state and impact before continuing or retrying.
Ticket diagnosticsCollect ticket JSON, copy redacted JSON and clear collected diagnostics.Use only redacted diagnostics when seeking assistance.

Excel source

SettingWhat it controlsHow to choose
Excel export / Read ExcelAccepts an .xlsx snapshot and reads its ticket columns. API access still supplies conversations, files and linked detail verification.Use the template and required-column guidance displayed by the importer. An Excel file alone is not a complete conversation/file migration.
Closed-date confirmationConfirms how a source without complete closed-date information should be treated when the option is offered.Inspect the source dates and the stated consequence before confirming.

Report-only activity source

SettingWhat it controlsHow to choose
Organization IDIdentifies the source report organization. This mode does not use an API token, test connection or make source API calls.Use the actual report’s organization identity.
CSV / ZIP report and Upload / validateUploads a .csv report or .zip containing the supported report and validates its columns and contents.Review required-column validation before proceeding.
Date orderDefines the interpretation of ambiguous dates in the report.Check a known source date rather than guessing month/day order.
Content fields and comments / Fields onlyChooses whether selected report comments and content fields become activities, or only field values are processed.Select the mode that matches the intended import, then inspect a sample.
Visibility confirmationControls whether selected report content may be treated as public; unconfirmed content stays private.Explicitly verify the source visibility before permitting customer-visible content.
Author matching / Report ownership confirmationOptional author matching and confirmation that the supplied report belongs to the intended organization.Resolve ambiguous identities and confirm ownership before starting.

Behavior to know

  • API resumes require re-entering a token for the same organization; saved checkpoints do not store the token.
  • Unmatched owners remain unassigned in the fallback queue. Ambiguous customer/contact matches require selection.
  • Report-only import covers selected report comments, not attachments or full history, and keeps content private unless explicitly confirmed.
  • For an Excel snapshot refresh, upload the fresh source and choose the appropriate update mode.
  • Continue applies to the selected saved run. Review its organization, mode, mappings and checkpoint before resuming.
  • Excel validation accepts up to 10 MiB and 50,000 tickets. New imports use the source Ticket Number in the TS- Case ID: for example Ticket Number 4821 becomes TS-4821. When no number exists, the API ID is the fallback. The API Ticket ID remains the matching key for repeat imports. Earlier imported Cases may retain their old identity; a conflicting number is reported without overwriting another Case. Verify the actual identifiers before customer communications.

Recommended use

  • Preserve the source export and migration evidence. Identify the selected run, source mode, mappings and saved checkpoint before continuing or retrying.
  • Reconcile representative customer matches, Case/activity visibility and failures before expanding the scope or updating existing records. A completed run counter alone does not establish a successful customer migration.
  • Plan the cutover and any follow-up run explicitly. Use this importer’s actual preview, run and recovery controls; do not treat it as a continuously synchronized integration with a generic removal action.

Worked example

  1. Connect and preview a small set of representative tickets.
  2. Set fallback routing and map customer, ticket and activity fields.
  3. Run the narrow sample and reconcile records and failures.
  4. Expand scope only after reviewing ambiguous customer matches and visibility.

Troubleshooting

ProblemWhat to check
API or Excel connection failsConfirm the exact TeamSupport organization and current API token. Excel mode also needs API access; report-only mode does not.
The Excel file is rejectedUse the supported export format and validate it with Read Excel. Keep within 10 MiB and 50,000 tickets; inspect the reported validation problem before splitting or changing the export.
A report date is ambiguousChoose and verify Date order using known source examples before importing. Do not infer the order from one ambiguous date.
A customer or owner is not matchedReview the actual identity evidence and mappings. Resolve ambiguous customer/contact matches; unmatched owners use the documented fallback rather than a guessed identity.
Imported visibility is wrongReview source mode and explicit visibility confirmations. Report-only content remains private unless deliberately confirmed otherwise.
A saved run asks for credentials againCheck the selected run’s organization and mode. Re-enter the token for API/Excel and Continue only after reviewing its checkpoint and mappings.
The report did not import attachments or full historyReport-only mode imports the selected report content. It is not an API-history or attachment migration.
Case identifiers differ from source ticket numbersNew imports use the Ticket Number for the TS- Case ID, falling back to the API ID when no number exists. Existing imports can retain earlier identifiers. Compare source number, API identity and the run reconciliation; resolve identity conflicts before retrying.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

Was this article helpful?