---
schema_version: "1"
id: 72efb5410ece384e3079602c296c626899c53f88f2ae9f5d8c1759dfa8c41d99
title: Other Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/ec_other_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.ec_other_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 463437a1b0712f86626f9e35488f2463e67a4b64edb9292149abf48f4050f014
description: Review these additional considerations before you migrate your data to Education Cloud.
products:
  - Education
release: "264"
---
# Other Considerations

Review these additional considerations before you migrate your data to Education Cloud.

- Technical debt: Run Salesforce Optimizer to identify potential issues, and address them. The common causes for issues are:
    - Object automation across workflows, flows, and triggers.
    - Custom object and custom field usage that leads to running against limits, or empty fields.
    - Sharing models and sharing rules that affect legacy objects.
    - Outdated installed packages.
- Current customizations: Objects might behave differently based on how objects relate to person accounts. Review the information that relates to contact records and person account records.
- Current integrations:
    - Replicate primary integrations with considerations for source objects and contact profiles.
    - Test integrations to ensure that records can be created and updated after account-contact pairs are converted to person accounts.
- Table-Driven Trigger Management (TDTM):
    - Avoid TDTM as it isn’t compatible with Education Cloud.
    - Deactivate existing trigger handler records before you migrate your data to Education Cloud.
    - Transform TDTM automations and remap them to Flow or Apex-based solutions by using trigger handler best practices. Use One Per Object designs to maximize efficiency and execution control.
    - Consider these steps when you migrate your data from a managed package environment with TDTM:
        - Review which trigger handler records are active.
        - Review the automations that need to be migrated to Education Cloud.
        - Evaluate custom TDTM classes and trigger handler records for applicability or improvement.
- Integration with Marketing Cloud:
    - Migrate the subscriber keys if the person account ID in Education Cloud is different from the contact ID or lead ID in Marketing Cloud.
    - Use a multi-org connector to migrate to a new org.
    - Reimplement Marketing Cloud Connect for new objects and triggers if required.
    - Consider that the Marketing Insights for Sales Cloud App dashboard might not work.
- Storage limits: When migrating data, the data is copied and not moved. As a result, your org’s data storage will reflect both your original data and copied data that is created by the migration kit. Expect data bloating for frequently used objects during the migration.

SEE ALSO:

- [Data Processing Engine Limits](https://help.salesforce.com/s/articleview?id=sf.reference_data_processing_engine_limits.htm&type=5)
- [Improve Your Implementation with Salesforce Optimizer](https://help.salesforce.com/s/articleview?id=xcloud.optimizer_introduction.htm&type=5)
- [One Per Object Flow Design Pattern](https://admin.salesforce.com/blog/2022/automate-this-tom-hoffmans-one-per-object-flow-design-pattern)
- [Automate Your Business Processes](https://help.salesforce.com/s/articleview?id=sf.extend_click_process.htm&type=5)
- [Subscriber Key in Marketing Cloud](https://help.salesforce.com/s/articleview?id=mktg.mc_es_subscriber_key.htm&type=5)