ControlMap does not currently offer a direct migration path, native integration, or one-click import from any GRC platform. You can use AI-assisted workflows with the ScalePad MCP and an available source-platform API or connector, import supported records with ControlMap CSV templates, or recreate information manually.

AI tools may help automate parts of the transfer, but the data you can move depends on the source platform’s capabilities, available ControlMap API endpoints, supported CSV templates, permissions, and how closely your source data matches ControlMap’s fields. Review what you need to move before you begin.

Choose an import method

Use the ScalePad MCP and AI tools

The recommended programmatic route is to use the ControlMap API capabilities with tools such as Claude or other compatible AI assistants. The ScalePad MCP makes supported ScalePad data and actions available from compatible AI tools, so you may not need to write API calls or build every step yourself.

The ScalePad MCP is listed in Anthropic’s MCP Marketplace. To connect it in Claude, open the connector directory, search for “ScalePad,” select it, and authenticate. You do not need to install software locally or set it up with a configuration file. For more information, see Getting started with ScalePad MCP.

1. Review the ControlMap API developer documentation to check the available endpoints, authentication requirements, and limitations.

2. If the source GRC platform offers an MCP connector or an API that your chosen AI tool can access, connect to it using that platform’s supported method.

3. Use Claude, Copilot, or another compatible assistant to help review the source data, map fields, and transfer records through supported API actions.

4. Review the mappings and verify the resulting data in ControlMap before relying on it.

Depending on the source platform’s tools and API, you may be able to automate much of the work with minimal development experience. The amount of automation varies by platform, permissions, data type, and supported API operations. The MCP and API are not ready-made migration services or direct GRC-to-ControlMap connectors; they can only work with supported data and actions.

Import supported records with CSV templates

Use CSV templates to transfer supported records through ControlMap’s import workflow. ControlMap supports CSV imports for records such as assets, vendors, risks, and people. Evidence records may also be imported when the source data is compatible with the Evidence template.

1. Export the relevant data from your source GRC platform.

2. In ControlMap, open the section for the data you want to import and download its CSV template from the import or upload workflow.

3. Match the exported fields to the columns in the ControlMap template. Adjust the data to fit the template’s required structure and values.

4. Import the completed CSV into the corresponding ControlMap section.

5. Review the imported records in ControlMap and correct any missing or mismatched information.

Upload supporting evidence files separately through the ControlMap interface; a CSV import does not automatically transfer file attachments. ControlMap Copilot may also help expedite evidence work: upload multiple evidence documents for Copilot to review and suggest mappings, then review its suggestions. Learn more in ControlMap Copilot.

Recreate data manually

Some information cannot be imported directly with a CSV template, or may not be supported by the API. Recreate that information in ControlMap using the source platform’s export as a reference.

Completed framework assessments, objective responses, assessment comments, and full-fidelity mappings cannot currently be imported directly from another platform. Configure the relevant frameworks in ControlMap, then manually enter the assessment details and rebuild mappings as needed.

Plan and validate the transfer

1. List the information you need to move and decide which import method fits each data type.

2. Keep the source exports available as a reference while you import or recreate data.

3. Confirm that supported records and manually recreated information appear correctly in ControlMap.

4. Resolve gaps before relying on the imported data for compliance tracking or reporting.

Because ControlMap does not provide a direct migration path from another GRC platform, some manual preparation and verification may be required even when AI tools assist with API or CSV work.