Skip to main content
Use LoopIQ imports to create supported records from CSV files or a database dump. Export availability varies by deployment and record type; do not assume that the import workspace provides a general export endpoint.

​
Before you begin

Make sure:
  • you know the source records and target LoopIQ record types
  • the file contains only data approved for the selected organization
  • you selected the correct organization and team
  • target users, statuses, and custom fields exist where needed
  • you can review validation and value mappings before creation

​
Import a CSV file

  1. Open Import / Export and create an import job.
  2. Select the target record type shown in your deployment.
  3. Upload the CSV using the signed upload link.
  4. Confirm Upload complete so LoopIQ can start analysis.
  5. Review detected columns and proposed field mappings.
  6. Map values such as statuses, priorities, teams, and assignees.
  7. Validate the mapping and resolve errors or warnings.
  8. Start the import.
  9. Follow live progress until analysis and import finish.
  10. Open the target LoopIQ area and validate record counts and a sample of records.
Assignee choices are limited to eligible members of the target team. Where supported, LoopIQ can derive a team from the selected assignee and otherwise use the importing user’s team as a fallback. Review the resolved team before creating records. Completion notifications can be sent after analysis or import. A notification is not a substitute for checking final row counts and errors. Audit history attributes the import to the authenticated importing user.

​
Import a database dump

Use the database-dump workflow when a relational source contains several related models.
  1. Create a database-dump job and upload the supported dump file.
  2. Confirm the upload and start analysis.
  3. Review discovered tables and the proposed target models.
  4. Select the models to import and deliberately skip tables that should not create LoopIQ records.
  5. Review column mappings for each selected model.
  6. Analyze and approve value mappings, including user, team, status, and relationship values.
  7. Start the multi-model import.
  8. Follow live progress for each model and review partial failures before retrying.
  9. Validate relationships and a sample from every imported model.
A successful discovery phase does not create records. Do not start the multi-model import until each selected model has an approved mapping.

​
Prepare a Jira migration

The Jira workflow provides readiness scoring and migration templates; it does not execute a live Jira synchronization. See Prepare work migration from Jira.

​
Troubleshoot an import

  • A 403 or 404 can mean the job belongs to another organization or is outside your role scope.
  • If analysis does not start, confirm that Upload complete was recorded.
  • If users are missing from value mapping, confirm they belong to the selected team.
  • If counts differ, review skipped rows, validation errors, and per-model status instead of rerunning immediately.
  • If progress stops, check the final job status before submitting a duplicate import.