Fields
Migration Center is in beta. It may not be turned on for your account yet. To request access, contact Paminga Support.
The Fields phase of Migration Center brings your Marketo data model into Paminga. It matters well beyond the fields themselves: when your forms, landing pages, and emails are converted later, every {{lead.…}} and {{company.…}} token in them is translated through the mapping you build here.
Discover Your Fields
Click Discover Fields. Paminga reads your Marketo lead fields and company fields and lists each one with its object, Marketo name, and Marketo type.
Discovery does some of the work for you:
- Auto-matching: a Marketo field that clearly matches an existing Paminga field (standard or custom) is set to map onto it, with a confidence percentage beside the match. Confirm it or pick another field.
- Sensible defaults: well-known Marketo standard fields get a sensible starting decision (for example, phone maps to Work Phone and lead status maps to Lead Stage). Other custom fields default to being created, and other standard fields default to being excluded.
- Drop-down options from your forms: Marketo doesn't store option lists on its fields, but your Marketo forms do. Paminga reads the options used across all your forms, and any field that turns up two or more options arrives already set up as a drop-down with those options filled in.
- Canonical mappings: a handful of fields are pinned to their Paminga equivalents and marked Canonical. Those mappings can't be changed.
Each Paminga field can be the target of only one mapping, so if two Marketo fields claim the same Paminga field, the stronger match keeps it.
Click Re-discover any time your Marketo field model changes. It refreshes the field list and never touches your decisions. A field deleted in Marketo drops off the list.
Decide Each Field
Every field gets one of three decisions in the Decision column:
| Decision | What happens when you migrate |
|---|---|
| Create new | A new Paminga custom field is created on the object you choose (Contact or Account), with the type shown in the Paminga Field column |
| Map to Existing | The Marketo field is linked to a Paminga field you pick. Nothing is created; the link is what later steps use to translate tokens |
| Exclude | The field is left behind |
Drop-Down Fields
For a field you're creating as a drop-down, open its options to review or edit them. The drawer is the same editor you use in Drop Downs, and your edits stay a draft until you migrate. A drop-down field needs at least one option before it can be migrated.
You can also turn a text field into a drop-down here, which is handy for a field that should always have been a picklist.
Lead Stage
A Marketo field mapped onto Paminga's Lead Stage needs your Lead Stages funnel in place before it can migrate. Use Set up Lead Stages on that row. Lead Stages are shared across your whole account, so changes made in that drawer save immediately.
Stage and Migrate
Fields move through four tabs:
| Tab | What's in it |
|---|---|
| Unmapped | Your backlog: everything not yet staged, migrated, or excluded |
| Ready to Migrate | Fields you've staged for the next migration |
| Migrated | Fields that have been created or mapped in Paminga |
| Excluded | Fields you're leaving behind. Select any and click Unexclude to bring them back |
Check the fields you're happy with on the Unmapped tab and click Ready to Migrate to stage them. Then click Migrate Fields in the bottom bar. Only staged fields are processed; the rest stay under Unmapped for another pass.
That lets you migrate in batches, starting with the fields you're sure about and coming back for the ones that need a conversation with your team.
Migrating is safe to repeat. A field that's already migrated is skipped, and if a Paminga field with the same name already exists, Paminga uses it rather than creating a duplicate.
What Completes This Phase
Fields is complete once a field migration has finished successfully. You can keep migrating more fields afterwards. New fields get added in Marketo during a migration, and you can re-discover and migrate them at any time.
Assets stays locked until Fields is complete.
