Bring your work into Scoped

Before you start

It’s a one-time move from a CSV file, not a live connection: nothing stays in sync with the old tool afterwards.

What a CSV can carry

A supported export can bring over the issue fields in the file, including identifiers, titles, descriptions, status, priority, people, projects, and related planning fields where present. The file decides what can come across.

• Comments and past activity can’t be rebuilt from a CSV.
• Attachments aren’t carried by a CSV.
• People named in the file may need matching to their Scoped accounts.

How the move works

1. Export your workspace to CSV from the tool you use today, with an admin account so nothing is left out.
2. Contact support with the tool’s name and the Scoped workspace the work should go to. Wait for support to explain how to share any required file.
3. Review with us what the file can and can’t carry before anything is imported.
4. Agree how the people in the file match members of your workspace. Nothing is guessed.

Review the imported work

1. Compare a few issue identifiers, titles, statuses, and owners with the old tool.
2. Check projects, teams, and any relationships you expect.
3. Go through any unmatched people with us and settle who they are.
4. Keep the original export until your team has accepted the results.

If something is missing

First check whether the CSV contained the missing field. Comments, attachments, and old activity are known limits of a CSV, so importing again won’t bring them back. Send support the specific issue identifiers you’re checking.