LN Personalization Migrator Move user personalizations between LN environments

Convert a personalization export

Upload the zip you exported from the old environment, map each old user to its new one, and download a zip ready for Import Personalizations (ttaad7202m000) — same file names, all at the root of the archive.

  1. 1

    Choose the exported zip

  2. 2

    Connect the tenants optional

    Pick the tenants to look people up in. The new tenant turns the right-hand column into a searchable list of names; the old tenant labels each ID in the zip with who it belongs to. Connect both and the rows are matched on surname for you.

    Old tenant the one you exported from

    New tenant the one you are importing into

    Employee numbers are company-specific, so a filter saved on one is translated along with the user name. Both tenants are read with this company.

    Credentials are held on the server as secret files and never leave it. Nothing is uploaded from your machine.

  3. 3

    Map the users

    One row per user found in the zip. Tick the users you want in the import file and set who each becomes in the new tenant. Unticked users are removed from the output entirely — their records are cut out, not just left alone.

    Include Old user in the old tenant New user in the new tenant
  4. 4

    Convert and download

What the tool changes

Only username= in the personalization_user_<pkg>_01 files is rewritten. Everything else, including the encoded <blob> layout payloads, is copied through byte for byte, and the XML is never reformatted.

ExportConfiguration_h is never modified. It is the export’s own header — who ran it, when, and the selection used — which LN keeps for reference when an import goes wrong. Rewriting it would falsify the record of what was actually exported, so it passes through untouched and the user range it names is left alone.

When several users are mapped at once the replacement happens in a single pass, so mapping a → b and b → c in the same run rewrites each name exactly once. An a never becomes a c.

Excluding a user removes their whole <user>…</user> element from every file, so none of their records reach the new tenant. The surrounding structure is left exactly as LN wrote it — a session that ends up with no users keeps its empty <users> container, the same shape LN already uses for <companies/> and <demRoles/>.

User names come from each tenant’s Infor Federation Services directory, whose lnUser property is the LN login code — the same value as tccom001.loco.

With both tenants connected, each row is matched on surname: one hit fills the new user in, and if several people share a surname it narrows by first name, then asks you to pick from just those people. An auto-filled ID is highlighted and marked “check it”, because a shared surname is not proof of the same person — typing or picking anything yourself clears the mark.