Separate source records, contact identities, relationship evidence, scores, reports, configurations and records written into your CRM. Retaining a local record does not automatically grant unrestricted rights to every underlying licensed dataset.
Ask for field lists, formats, source references, history, costs and timing. Check whether another system can use the exported information; a vendor-specific score may require reinterpretation even when it is exportable.
Document retention after termination, backup handling, derived data treatment and relevant legal obligations. Confirm how integrations are disconnected and what evidence of completion will be provided.
Preserve permitted operational records and pending requests. Test whether a replacement can reconstruct required evidence and workflows. Do not assume a fixed migration period or that all vendors expose identical history.
For Orbb, rely on current agreement terms and documented export capabilities. The right question is what you can lawfully retain and use, what you would lose and how the transition will work in practice.