Migration Center
Migration Center is in beta. It may not be turned on for your account yet. To request access, contact Paminga Support.
Migration Center moves your marketing operation from Marketo into Paminga. It reads your Marketo instance through its API, shows you everything it found, and lets you decide what comes over and where it lands before anything is created in Paminga.
It brings across the parts of a Marketo instance that take the longest to rebuild by hand:
- Users and roles: your team's accounts, with roles translated from Marketo permissions
- Fields: lead and company fields, mapped onto Paminga fields or created as new custom fields
- Folders and programs: your folder tree, with programs becoming Marketing Campaign folders
- My tokens: carried over as folder tokens, inheritance intact
- Forms, landing pages, and emails: converted into native Paminga assets you review and approve one by one
A migration is rarely a single afternoon. Migration Center is built for that: every step can be revisited, re-run, and refined for as long as the migration takes.
Before You Start
Migration Center needs a connected source platform. Today that is Marketo. Connect Paminga to Marketo on the Integrations page first; until you do, Migration Center shows a prompt that sends you there.
You'll also want two CSV exports from Marketo Admin → Users & Roles for the first step: the Roles & Permissions file and the User List. Marketo's user-management API isn't available on every instance, so users and roles come in by file rather than over the API.
Find Migration Center
Migration Center is in Account Settings. Click Migration Center in the Account Settings menu, or click Open Migration Center on the Marketo card on the Integrations page.
The Migration Lane
Migration Center is organized as five phases, in the order a migration actually needs them:
| Phase | What it does |
|---|---|
| Users & Roles | Import your Marketo roles and users, then create them in Paminga so later work is owned by real people |
| Fields | Discover your Marketo field model and decide, field by field, to create, map, or exclude |
| Folders & Programs | Mirror your Marketo tree, decide what migrates, and map it onto your Paminga tree. Programs, my tokens, and workspace access come along with it |
| Brand | Give each workspace a Brand Kit so converted assets look right the first time |
| Assets | Convert forms, then landing pages, then emails, and review each one before it goes live |
The overview shows one card per phase, with its state, a summary of its most recent run, and when it was last discovered or migrated. Click a card to open that phase. The Continue button in the bottom bar always points at the next phase that is ready for you.
Why the Order Matters
Some phases depend on others, and Migration Center enforces the dependencies that matter:
- Folders & Programs opens once Users & Roles is complete. Workspace access is granted to the teams built from your users, so the users have to exist first.
- Brand opens once Folders & Programs is complete, because Brand Kits attach to workspaces and workspaces are created by the folder migration.
- Assets opens once Folders & Programs, Fields, and Brand are complete. Converted assets land in your migrated folders, their merge tokens resolve through your field mapping, and they inherit their workspace's Brand Kit.
Fields has no prerequisite, but Migration Center reminds you that users should be migrated first.
A locked phase stays visible on the overview with a note saying what it's waiting for. Once a phase has been migrated, it never locks again.
Phase States
| State | Meaning |
|---|---|
| Locked | A prerequisite phase isn't complete yet |
| Available | Ready to work on; nothing migrated yet |
| Running | A discovery or migration run for this phase is in progress |
| Partially complete | Some of the phase's migrations have run, but not all of them (for example, roles migrated but users not yet) |
| Complete | Every migration in the phase has succeeded at least once, or you've deliberately skipped it |
"Complete" doesn't mean "finished forever." You can return to any phase, re-discover, and migrate again as your Marketo instance changes during the cutover.
How Every Phase Works
The phases differ in what they move, but they share the same rhythm.
Discover, Decide, Migrate
- Discover: Paminga reads the current state of your Marketo instance. Re-discovering refreshes what Paminga knows and never touches the decisions you've already made.
- Decide: you choose what comes over and where it goes. These decisions are a draft, held on screen. Nothing is written until you migrate, and Migration Center warns you if you try to leave with unsaved changes.
- Migrate: one button, labeled with what it's about to do (for example, Migrate 12 Fields), saves your decisions and starts the run.
Runs and the Bottom Bar
Every discovery, migration, and conversion is a run that works in the background. You can keep working, move to another phase, or leave the page while it runs.
The bar along the bottom of Migration Center shows the active run's progress, with a Stop button if you need to halt it. Expand it to see your run history: each run's status, when it was queued, how long it took, and its details.
Re-running Is Safe
Migrations are designed to be run more than once. Anything already created in Paminga is recognized and skipped rather than duplicated, and a failure on one item is recorded on that item while the run carries on with the rest.
What Migration Center Doesn't Move
- Activity history: opens, clicks, form fills, and other behavioral data stay in Marketo
- Smart campaigns and flows: campaign logic isn't converted, which is also why a few Marketo token types (like score and Salesforce campaign tokens, which only mean something inside a flow step) aren't created
- Program members: programs arrive as Marketing Campaign folders, but the people in them don't come with them
- Brand Kits: Marketo has no equivalent to convert, so you build them in the Brand phase
Who Can Use Migration Center
Migration Center is available on accounts where the beta is turned on. It doesn't have a dedicated permission of its own yet, so any signed-in user on those accounts can reach it. Because it creates users, roles, fields, and folders across your whole account, keep it in the hands of the people running your migration.
