Before your first migration
Prepare the following. Setup takes about 10 minutes.
Accounts and password resets come from an admin.
Profile, password, two-step sign-in and data handling. The theme setting is in the account menu.
Required for all users.
Every sign-in requires a 6-digit code from your authenticator app. If you lose your phone, sign in with a recovery code or ask an admin to reset your two-step sign-in. You then set it up again.
What is stored, and where.
Reports you submitted, newest first, with their status. The service owner reviews every report.
To report a problem or suggest an improvement, select Report a problem at the bottom of any page.
Nothing is transferred until you start the run on the Review step. This migration becomes a step of a plan: on Review, Add step to plan saves it instead of starting it.
Document Control documents can also be browsed, attached and detached under Document Control.
To upload from another folder, change the folder here before loading a mapping file. Pending files keep their folder.
A connection stores the Intelex site address and SFTP details. The last used connection is preselected.
Required once per session. Never written to disk. Released when your last session and active runs end.
API keys are created by your Intelex admin.
Password for the SFTP account that can read the files.
This connection uses a different SFTP server as the download destination. Required once per session, never saved.
A plan step never downloads originals: an Original column in a file is ignored here.
The documents of , each with its current released file. Tick the ones to download, then add them to the list.
Load 0 files. Nothing is transferred until you start the run.
Review the summary, then start the run. You can pause or stop at any time. Completed files are not repeated.Review the summary, then add this migration as a step of . Nothing is transferred now; the step runs in order when you run the plan.
Estimated duration:
You can close this page after the run starts. The run continues on the server.The step is saved with its files. Add the next step from the plan page.
Estimate: how long would this have taken manually?
Do not include customer data.
Thank you for your feedback.
Start a run with New migration to monitor it here. Runs continue on the server if you close this page.
Another run is using the server. A run you start joins the queue and starts automatically. It appears here when it begins.
Runs / Live
| Time | File | Reason |
|---|
No issues.
| Time | File | Record | Status |
|---|
/ Run
Runs started from your account. Run records contain file names, sizes, statuses and error text, never file contents. To give feedback on a finished run, open its row menu and select Give feedback.
Every file processed from your account, with its latest status and the failure reason where applicable.
A plan runs several migrations in order, one after the other, and gives one report. Each step is a migration you set up with the wizard.
Make a plan, add each migration as a step with the wizard, review the list, then run it once. The steps run in order and you get one report. Keys can be kept so the plan finishes after you sign out.
Documents of the connection in use, each with its current released file. Add documents to the download list and start the download as usual, or set and clear the File field of a document.
Intelex listed no Document Control documents for this connection. Check that the API key can read Document Control, then Reload.
Nothing on this page has been checked against a live Intelex site yet. The columns are read from the fields Intelex sends, under the names it uses; if a title or revision reads wrong, open the document and send its field names to the service owner.
Saved Intelex sites and SFTP servers. Each detail is entered once, here. API keys and passwords are not stored in a connection.
This connection is not active. Selecting Use this connection activates it and releases the API key and password entered for this session.
Add your Intelex site address and SFTP server once. Select the connection when you start a migration.
Intelex rejects some file names: names that are too long or contain characters Windows does not allow. Suggestions keep the file extension. Saving changes the name in Intelex only; the file on the SFTP server keeps its name.
Names that Intelex rejects are listed here with a suggested replacement.
View all filesAdmins add users and help with sign-in. Admins cannot see other users' files, connections or runs.
Recovery lock: a password reset was completed and the user has not yet signed in with two-step sign-in. A different admin must reset their two-step sign-in.
Invite a user to share access. A one-time link is created for you to send to them.
Limits and modes for all users. Each section saves on its own and asks for your two-step code.
Each user picks a value up to this limit. Higher values can slow the server. Applies to the run in progress.
Effective value: 1.
This server allows up to 64 MB. Larger files are skipped and flagged. Applies to the next file.
Files up to 64 MB are accepted.
Dollars are computed on this server from this price. Users see estimates before a run and the cost after it only while the switch is on; they never see the price itself.
Between 10 and 60 minutes, accurate to about 1 min. A warning shows 1 min before sign-out.
Idle sign-out after 30 min.
One rounded line, for example "Over 5,000 files transferred". Anyone who opens the sign-in page can read it.
Off. The sign-in page shows no numbers.
Rounded totals of all users beside the form. Nothing per person or client. Small numbers are left out.
Off. All users can start runs.
140 characters left. Shown as plain text above every page.
Information only, up to 7 days ahead. It does not end maintenance; set the mode back to Off.
All runs on this service, newest first. Shows account names and masked connection details only, never files, folders or error text.
Adjust the filters or widen the date range.
How close the estimated time remaining shown on the Run page came to the actual duration, for completed runs. Times and sizes only.
No completed run with an estimate matches yet.
Every failure cause seen on this service, as counts and codes only: never file names, record IDs, folders or users. A flag you set here is shown beside the cause in everyone's reports; the app never sets one on its own.
Counts only. Flags and samples are set and seen by the service owner.
A cause appears here the first time a file fails with it.
Reports submitted from within the app, newest first. Each report includes the page, time, app version and last error shown; never files, keys or passwords.
Users submit reports with Report a problem at the bottom of every page.
Responses submitted after runs. Hours saved are self-reported. Comments are free text; a name is shown only when the user agreed to be contacted.
This week
of responses rated Good
Response rate
of feedback requests answered
Estimated hours saved (self-reported)
users' estimates of the equivalent manual effort
Responses by run outcome
Runs waiting to start, in order. Visible to the service owner only. Shows account names and size bands, never files or folders.
Runs started while another run is in progress are queued here in the order they will start.
How a migration works, what the mapping file contains, and what is stored where.
| Column | Value |
|---|---|
| Object | Type of record: the technical object name, for example EHS_IncidentObject, not the display name (such as Risk Specific Control) |
| RecordId | The Intelex record ID |
| FileName | Uploads: the name of the file on the SFTP server. Downloads: optional; the name to save the attachment as. |
| AttachmentId | Downloads only: the ID of the attachment to download |
Columns can be in any order, and other columns are ignored. Other names are matched automatically: Object Type or Object Name for Object; Object Record Id or Record GUID for RecordId; Attachment GUID, or Id when no other column is the attachment, for AttachmentId; Attachment Name for FileName (uploads also take Name or File when no other column is the file name). Upper and lower case, spaces, underscores, hyphens and dots do not matter, so an Intelex list view export (Object, Object Record Id, Id, Attachment Name) loads as it is. When a column is missing or two columns could be the same field, step 2 asks you to match them.
Ask your Intelex admin to create one for you and send it over a private channel. It must have access to every object in your mapping file.
No. It is never written to disk. It is held in memory until your last session and your runs end. Enter it again after that.
Yes. You can pause or stop at any time. Completed files are not repeated. Starting again continues with the pending files.
Intelex receives a duplicate attachment, which this app cannot remove. The Review step excludes files already uploaded.
Nothing is overwritten. The new copy is saved with _1 appended to the name.
Receipt of the file could not be confirmed. Check Intelex or the destination folder, then select Mark as uploaded or Retry.
Intelex limits name length and characters. Use Fix names.
Use a recovery code. If none are left, ask an admin to reset your two-step sign-in.
No. Admins manage users and sign-in only. They cannot see your files, connections or runs.
The link may be outdated, or the run or connection it referenced was removed.