Help Center
  • Home
  • Getting Started
    • Register with oAuth
    • Register with Email + Password
  • Formulas
    • Formulas
  • Migration Templates
    • Migration Templates
    • Setting up the Template
    • Magic ID
    • Running the Template
  • seeding
    • Summary
    • Data Types
    • Configuration
  • Jobs
    • Job Management
    • Migrate
    • Multi-Object
    • Upload
    • Mapping
    • Query
    • Preview
    • History
    • Retry
    • Rollback
    • Run Remaining
    • Wildcard Names
  • Formatting
    • Dataimporter Formatting
    • Replace Null Values
    • Deduplicate
    • Filter Data
    • Sample Data
    • Automation Control
  • Schedule
    • Schedule
    • Hour
    • Day
    • Month
    • Flow
  • Integrations
    • View Integrations
    • Database
      • Azure SQL Database
      • Heroku Postgres
      • MySQL
      • PostgreSQL
      • SQL Server
    • Storage
      • Dropbox
      • Google Drive
      • Google Sheets
      • OneDrive
      • S3
      • SFTP
      • SharePoint
  • Account Management
    • Billing
    • Access
    • Teams
    • Notifications
  • Security
    • Dataimporter Security
    • IP Addresses
    • Data Storage
    • Customer Managed Storage
    • Single Sign-On with Azure AD
    • Single Sign-On with Okta
    • Bring your own Key
  • Changelog
Powered by GitBook
On this page
  1. Migration Templates

Magic ID

PreviousSetting up the TemplateNextRunning the Template

Last updated 1 year ago

Using the Magic ID lookup relationships, Dataimporter can automatically perform a VLOOKUP on your behalf, to link related records from the source org, to the newly created records in the Target Org.

Let's run through the same example from the using the Contact object.

Under the Account lookup you will see that the mapping has been completed automatically for you, with the AccountId from the source org being mapped to the Account Lookup via MagicId in the Target Org.

What Dataimporter will do in the background, is take the source and target Ids of the parent records that were created, and perform a match, so that when the Lookup values are populated in the target org, they are the same records which existed in the source org.

MagicId can only be used to link objects which are included in the Migration Template, and the referenced object must be run before the current object.

If you try to include an object as a MagicId which is either not included in the Template, or is set to run after the current Job you will receive an error.

Previous document