Arc XP's content migration process

ANS is Arc XP's standardized, JSON-based content format, which includes various content elements such as headlines, body text, images, metadata, and more. You must be familiar with ANS because all content ingested into Arc XP must conform to its schema.

For more information, see:

Before initiating the migration, ensure you complete the following items:

Mapping your content involves correlating fields from your legacy CMS to ANS fields. This process is critical and involves the following items:

You can use the ANS Maps tools to create your content mapping. See Managing ANS maps.

An adapter is custom software that you own and operate. It serves as the middle ware between your source system and Arc XP. The adapt should:

The migration pipeline uses several stages:

When sending content to Migration Center, the JSON payload must follow this structure:

{
  "ANS": { /* ANS object */ },
  "circulations": [ /* Optional: circulation data for stories */ ],
  "operations": [ /* Optional: scheduled operations */ ],
  "arcAdditionalProperties": {
    "story": { /* Additional instructions for stories */ },
    "video": { /* Additional instructions for videos */ }
  }
}

Migration Center provides APIs to monitor the migration process. See the Migration Center API documentation to identify endpoints to monitor the progress of content through the pipeline and to identify and troubleshoot errors.

The inbound rate limit defines how many requests you can send to the Migration Center API per minute. This rate is fixed.

The inbound rate limit is 800 requests per minute.

The outbound rate limit is the rate at which Migration Center sends content into Arc XP's content administration APIs. These rates are adjustable but depend on the target system's capacity and require coordination with Arc XP.

You must coordinate outbound rate adjustments with Arc XP. Contact Arc XP Customer Support. Rate increases are not guaranteed and depend on infrastructure usage and provisioning.