Folders & Programs
Migration Center is in beta. It may not be turned on for your account yet. To request access, contact Paminga Support.
The Folders & Programs phase of Migration Center builds the skeleton your migrated assets will live in. You see your whole Marketo tree beside your Paminga Finder tree, decide what comes over, and drag it where you want it.
One migration brings across more than folders:
- Folders become Paminga folders
- Programs become Marketing Campaign folders, carrying the program's dates and their own member-status drop-down built from the program channel's statuses
- My tokens become folder tokens on the folders they belong to
- Workspaces become top-level workspaces, with access granted to the right teams
This phase opens once Users & Roles is complete.
Discover Your Tree
Click Discover Folders. Paminga reads your entire Marketo tree: folders, programs, and the forms, landing pages, and emails inside them. Click Re-discover later to pick up changes; your decisions and mappings are kept.
Two switches control what you see:
- Include archived: shows folders archived in Marketo. With it off, archived folders are hidden and are never swept in when you drag their parent.
- Show system areas: shows Marketo's built-in system areas alongside your own folders.
Decide & Map
The Decide & Map window shows your Marketo tree on the left (Source — Drag to Accept) and your Paminga tree on the right (Paminga Destination).
To bring something over, drag a Marketo folder or program onto a Paminga folder. That accepts the whole subtree for migration and maps it to that destination in one move. If you'd rather not drag, click the source folder, then click its destination.
To bring a Marketo folder over as a new top-level Paminga workspace, drop it on Drop here to migrate as a new workspace, or right-click it and choose Migrate as a New Workspace. You can also create an empty workspace on the spot with the Create a New Workspace button above the Paminga tree, and right-click the Paminga tree for the same menu you know from the Finder.
Once something is mapped, every node in it has its own decision:
| Decision | Result |
|---|---|
| Migrate | Created in Paminga |
| Archive | Created in Paminga, then archived |
| Exclude | Left behind |
Archive and Exclude apply to the node and everything under it, so you can accept a big subtree and leave one stale branch behind. Click the × on a mapping to remove it.
Forms, landing pages, and emails show in the tree as Migrated later. Folders only create the structure; the assets inside them are converted in the Assets phase. Only assets in folders you migrate are converted, so this is also where you decide which assets are in scope.
Migrate Folders
Your decisions are a draft until you click Migrate Folders in the bottom bar. Then Paminga:
- Creates your folders, programs, and workspaces in the places you mapped them. A folder that already exists at the same path in Paminga is reused rather than duplicated.
- Creates each program's member-status drop-down from its Marketo channel.
- Creates your my tokens as folder tokens, in the background. Marketo doesn't offer a bulk token API, so Paminga reads tokens folder by folder; a large tree takes a while, and the bottom bar shows its progress.
- Applies workspace access (see below).
You can keep working while this runs. Migrating again later skips anything already created.
How My Tokens Come Across
Paminga creates a token only where a folder or program actually defines it. Marketo reports every token a folder inherits as if it were the folder's own; Paminga compares each folder with its parent and only creates the ones that are new or overridden. The result behaves the way it did in Marketo: change a token on a parent folder and every folder that inherits it sees the change.
Text, rich text, number, date, and image tokens are created. A few kinds aren't:
- Score and Salesforce campaign tokens only drive steps inside Marketo flows, and flows aren't migrated
- Calendar (iCalendar) tokens have no Paminga equivalent yet
- Email script (Velocity) tokens are created later, during asset conversion, on the assets that use them
Nothing is lost: every token is read and recorded in full. The token run in the bottom bar shows a not created count; click it to see which tokens weren't created and why.
Workspace Access
If your Marketo instance has more than one workspace, Paminga recreates that partitioning with Teams:
- One Workspace: name team per Marketo workspace
- Each migrated user joins the teams for the workspaces they had roles in (users with access to all workspaces join every team)
- Each team is granted access to its workspace folder, with read or write access based on its members' Marketo roles
Access is only ever added. Existing team members and grants are never removed. A single-workspace instance needs none of this, so nothing changes.
What Completes This Phase
Folders & Programs is complete once a folder migration has finished successfully. Brand opens next.
