Migrate Data in K-12 Architecture Kit

Before You Migrate Data

Before migrating data to K-12 Architecture Kit, we recommend that you learn about the EDA data model. The EDA data model is the foundation of K-12 Architecture Kit, so it’s important to learn about it. Understanding which objects are available and how your data maps to them can help you decide whether to migrate all of your data or just some of it. If you’re migrating all of your data and are replacing a legacy system, follow the steps for installing and configuring K-12 Architecture Kit in a new org. If you’re integrating a legacy system with K-12 Architecture Kit, we recommend using a middleware tool to build the integrated system, starting with the standard EDA data model, then customizing it to accommodate the data from the legacy system.

Familiarity with the EDA data model also helps you decide whether you can use only existing K-12 Architecture Kit objects or whether you need custom objects. While you’re free to create as many custom objects as you need, we recommend using K-12 Architecture Kit objects instead of creating custom objects when possible, to make sure that you can use new tools and features as they’re released. For information, see Welcome to Your EDA Data Model Orientation.

After learning about the EDA data model, take some time to get acquainted with the automation that affects imported data and our Recommended Data Import Sequence for EDA.

Modify Your Settings

To make sure that you're able to merge data, review the prerequisites before migrating.

• In EDA Settings, turn off Record Type Validation.

• Disable these EDA triggers:

  • ACCT_CannotDelete_TDTM

  • ADDR_CannotDelete_TDTM

  • AFFL_CannotDelete_TDTM

  • BEH_CannotDelete_TDTM

  • CASE_CannotDelete_TDTM

  • CON_CannotDelete_TDTM

  • COUR_CannotDelete_TDTM

  • COFF_CannotDelete_TDTM

  • FACI_CannotDelete_TDTM

  • PReq_CannotDelete_TDTM

  • PREN_CannotDelete_TDTM

  • PPlan_CannotDelete_TDTM 

    See Disable Trigger Handlers for EDA.

You can turn these settings and triggers back on after merging your data.

If your batches time out before a merge completes, include fewer records in them. Batch size processing defaults to 200 records per migration, which can be too large if you have other existing automation.

Tip In most cases, we recommend that you work with a partner to migrate your data and to build customizations. If you don't work with a partner, be sure to migrate data to a Sandbox org before moving it to a Production org. To migrate data from an existing org to your fresh org, you can also Request an Org Swap.

For additional information about migrating data in Salesforce, see Migrate data from one organization to another in Salesforce Help.