Migration Hub: Review Data Before You Import

Migration Hub: Review Data Before You Import

Question: How can I move information from another system without importing the wrong columns or exposing private records?

The Migration Hub is a four-step process: Select Source, Upload Files, Map Fields, then Import. Treat the first run as a controlled review, not a bulk transfer.

Before you start

Prepare a copy of the source file that contains only the records you are authorized to import. Remove passwords, tokens, bank details, private notes, and columns you do not need. Do not use a live customer export as a learning example.

Step by step

  1. Open Migration Hub from the left menu and select New Import.
  2. In Select Source, choose the system or file type you are moving from.
  3. In Upload Files, add only the reviewed copy. Confirm the file is the intended version before moving on.
  4. Open Map Fields. Choose the target entity, such as customers, jobs, invoices, or another supported record type.
  5. For each source column, select the matching target field. Leave a field as Not Mapped when it should not be carried over.
  6. Read the required fields notice. Resolve missing required information before import.
  7. Review Unmapped columns carefully. The screen warns that unmapped data will be discarded.
  8. Use Back to fix the source or mapping when something is unclear.
  9. Check the acknowledgement about discarded columns, then start the import only after a second reviewer agrees the mapping is correct.

Mapping checklist

  • Each source column has one clear purpose.
  • Names, phone numbers, email addresses, and addresses are only imported when needed and authorized.
  • No credentials, secret links, or internal notes are mapped.
  • Required fields are resolved deliberately, not guessed.
  • A human reviews every discard warning before import.

Limitations

Mapping assistance can suggest a connection, but it cannot decide whether the source data is accurate, lawful to use, or appropriate to retain. Keep the original export private and use a small, synthetic test file whenever possible.

Next: Guides & Tips