Assets
Migration Center is in beta. It may not be turned on for your account yet. To request access, contact Paminga Support.
The Assets phase of Migration Center is where your Marketo content becomes Paminga content. Forms, landing pages, and emails are rebuilt as native Paminga assets, built with Paminga's own builders, so once you approve them they're as editable as anything you'd have created from scratch.
Nothing goes live on its own. Every converted asset arrives unpublished, waiting for you to review it, and you approve each one.
This phase opens once Folders & Programs, Fields, and Brand are complete. All three feed into conversion: assets land in your migrated folders, their tokens resolve through your field mapping and folder tokens, and they inherit their workspace's Brand Kit.
Three Steps, in Dependency Order
| Step | Why it's in this position |
|---|---|
| Forms | Landing pages embed forms, so forms come first |
| Landing Pages | Emails link to landing pages, so pages come before emails |
| Emails | Nothing depends on emails, so they come last |
Each step opens once the previous one is complete: every form converted and approved before Landing Pages opens, and every landing page before Emails. Archived assets don't count, since nothing converts them.
What's in Scope
Only assets in folders you chose to migrate in Folders & Programs are converted. If a step says nothing is in scope, include the folders that hold those assets in Decide & Map, then come back.
Convert
Each step starts with a convert button: Convert Forms, Convert Landing Pages, or Convert Emails. Conversion runs in the background, and assets appear in the review tree as they're created.
What happens to each type:
- Forms: Marketo has no form templates, so each form converts on its own. Fields resolve through your field mapping.
- Landing pages: each page is rebuilt from its own Marketo template and content, so every page keeps its own layout. Pages arrive with no address and unpublished, so no visitor can reach one until you decide where it lives.
- Emails: each email is rebuilt from its own template and content, keeping its layout, subject line, and sender.
A landing page or email with no Marketo template has no layout to rebuild into. Migration Center tells you how many there are before you convert, then skips them and reports them.
A failure on one asset is recorded on that asset, and the rest of the run carries on.
How Tokens Are Translated
Every Marketo token in your content is translated into a Paminga equivalent:
| Marketo token | Becomes |
|---|---|
{{lead.…}} | The Paminga contact field you created or mapped in Fields |
{{company.…}} | The Paminga field you created or mapped in Fields for that company field |
{{my.…}} | The folder token created by the folder migration |
{{system.…}} link tokens | Paminga's equivalent links, such as unsubscribe and view as web page (Paminga has no forward-to-a-friend link, so that one isn't carried) |
| Email script (Velocity) tokens | A Liquid token on the asset that uses it |
A token Paminga can't resolve is never left in your content as raw text. It's replaced with the default value you gave it in Marketo, and the replacement is recorded in that asset's conversion notes.
Review
Once the first asset converts, the step becomes a review screen. On the left is your Finder tree, filtered to that step's asset type; click an asset to see it on the right.
Each asset shows its status:
| Status | Meaning |
|---|---|
| Converting | The run is still working on it |
| Failed | Conversion failed. The error is recorded on the asset |
| Migrated | Converted and waiting for your review |
| Approved | You've signed it off |
Conversion Notes
The Conversion Notes bar at the bottom of each asset lists what the converter couldn't carry across exactly:
- Notes counted as to review are the ones worth your attention: something was lost or needs a decision. Some come with a one-click fix; others you Dismiss once you've dealt with them.
- Notes counted as deliberate are intentional differences, like a dropped Marketo-only setting or Paminga's own Country list replacing a hand-typed one. They're correct by design and need no action.
Edit, Brand, and Approve
- Edit opens the asset in its Paminga builder without leaving Migration Center. You can save changes there, but publishing and sending are switched off, so a half-reviewed asset can't go live by accident.
- The Brand Kit picker shows which kit the asset uses. It inherits its workspace's kit, and you can change it per asset here.
- Approve signs the asset off:
- Forms: Approve also publishes the form. Choose Approve and Keep as Draft from the button's menu to sign it off without publishing.
- Landing pages: Approve signs the page off only. To publish it, give it an address in the Landing Page Builder (see Publishing & Hosting).
- Emails: Approve signs the email off only. Nothing becomes sendable until you publish it. If your account uses Approvals, converted emails start as drafts and travel your normal approval path; if it doesn't, they arrive approved but unpublished.
- Withdraw Approval reverses a sign-off.
Click Next Form (or Next Landing Page, Next Email) in the bottom bar to jump to the next asset that still needs review.
Skipping a Step
If you don't want to migrate a type, or don't want to approve every remaining asset, skip the step. Skip Migrating Forms (or Skip the Rest of Forms, once some are approved) marks the step done and opens the next one.
Skipping never deletes anything: approved assets stay approved and live, and unapproved ones keep their converted drafts. You can come back and convert or approve at any time.
Skipping an earlier step has a cost, and Migration Center warns you about it. Landing pages converted without their forms, or emails converted without their landing pages, will reference assets that were never created in Paminga, and those references have to be repaired by hand.
