Migration assessment services.
Example Findings
Not real customer data.
One business area
| Domain | Complexity | Risk |
|---|---|---|
| Standard objects | ||
| Custom objects | ||
| Fields | ||
| Relationships | ||
| Record types | ||
| Picklists and controlled values |
Complexity describes the migration work. Risk combines complexity with business impact.
4,860 items assessed
4,860 of 5,120 items assessed. 260 items need further assessment and are not included in these counts.
From finding to action
Examples of specific migration actions.
Customer and CRM data
01 / 06Redesign required
A junction relationship connects two records and carries details of its own.
Choose a junction object or two labeled association links. Preserve the relationship details and define how duplicates will be handled.
Processes and automation
02 / 06Configuration required
One approval step, with no delegated approval, record locking, external actions or calls to other automations.
Define who can submit, who approves, and the approve/reject actions. Configure the reviewed workflow and preserve the approval state and audit trail.
Activities and files
03 / 06Configuration required
Email history can be represented without dependencies on live mailbox or delivery behavior.
Log each historical email once, without sending it. Preserve participants, attachments, ownership and record links using the approved identity and deduplication mapping.
Customer and CRM data
04 / 06Configuration required
The object needs a custom schema, properties and associations in the destination.
Confirm custom-object entitlement and capacity, then create the schema and associations. Map record identities and remap dependent workflows and reports.
Users, ownership and access
05 / 06Configuration required
An ownership assignment has dependencies; its destination owner identity and active status are confirmed.
Map the source owner to the approved destination owner ID before loading dependent records. Check routing and access separately; ownership alone does not preserve permissions.
Processes and automation
06 / 06Configuration required
An active escalation notifies an owner once, without a business-hours clock or repeated escalation.
Approve the time threshold and owner mapping, then configure the delayed workflow. Decide what happens when the record changes or closes.
Before the move
Get updates about OpenExit and its launch.
