> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/okta-ma/operations/imports-and-exports.md). # Imports and exports What each run operation does against Okta, and what to watch out for. ## Full Import Keep a periodic full import in your schedule. It's the only operation that can detect an object permanently deleted from Okta, because a delta import can only report on objects Okta can still return. Run one after changing the group import settings on the Global Parameters page, since those change which groups Okta is asked for. ## Delta Import The watermark is the Okta `lastUpdated` value. Groups carry `lastMembershipUpdated` as well, so a membership change is picked up even when the group profile itself has not changed. A delta import can't confirm a permanent delete. Use a full import for that. ## Export Exports are not transactional, and this is worth designing around. A single object's export can involve several API calls, and any one of them can fail after the earlier ones have succeeded: * A user can be created and its activation fail. * A user can be created and a suspension fail. * A group can be created and a membership assignment fail. When a create reports an error, check Okta before retrying, as the object may have been created. Import and reconcile it rather than exporting the create a second time, which Okta will reject as a duplicate. ## Rate limits Every import and export consumes the Okta org's rate limit, and so does everything else using that org. The management agent has no way to reserve capacity. Import cost is driven mostly by object count and by the per-object attributes: `enrolledFactors` and `availableFactors` each cost one call per user, and group `member` costs one call per group. The management agent log records the enumeration and per-object processing time separately, which lets you tell a slow Okta listing apart from slow per-object processing. See [reading import diagnostics](/okta-ma/administration/logging-and-monitoring.md#reading-import-diagnostics). Page size and concurrency can be tuned from [Advanced settings](/okta-ma/administration/advanced-settings.md), but read the timings first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lithnet.io/okta-ma/operations/imports-and-exports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.