Attachment Migrator Sign in

For Intelex consultants

Move Intelex attachments without the hand work.

Upload files from an SFTP server to Intelex records, or save attachments back out, from one mapping file. Review first, then run.

Access is by invitation. Ask the person who runs this service for one.

How it works

Three steps, in the order you would do them by hand. Nothing is transferred until the third.

  1. 1

    Connect

    Choose a saved connection, which names the Intelex site and the SFTP server. You type the API key and SFTP password once per session. They are never saved.

  2. 2

    Review

    Load your mapping file. Each row is checked in your browser and shows what will happen to it before anything does.

  3. 3

    Run

    Start when you are ready. Progress is live, file by file. Pause or stop at any time, and retry what failed.

What you get

  • Both directions

    One mapping file attaches files from the SFTP server to Intelex records, or saves attachments from records back to the server.

  • A folder per file

    A column in the mapping file names a destination folder for each file, so one run can sort files into many folders.

  • A report for every run

    Each run keeps its own page with what was transferred, what failed and why, and the settings used. The page stays after the run ends.

Nothing moves until you start a run.

It handles your clients' data, so the defaults are cautious.

  • Keys stay in memory

    API keys and SFTP passwords are held in memory for your session only. They are never written to disk.

  • Review first

    Every row of the mapping file is shown with its planned action. Problems are flagged before the run starts.

  • You start it, you stop it

    A run begins only when you press Start. Pause or stop at any time. Files already transferred are listed.

  • Two-step sign-in

    Every account signs in with a password and a code from an authenticator app. Accounts are created by an admin.

Made for the consultant doing the migration.

A client migration usually means one mapping file per Intelex object, each with its own folder on the server. The tool takes them one at a time, with a review before each run and a report after it.