Replace recurring copy-paste between two systems

Set up automation to copy field values between systems when new records appear, eliminating manual retyping.

For anyone moving the same fields twice a week · 8 steps · 7 min

How it works today.

Every Tuesday and Friday, you check System A for new customer records that came in overnight. You copy the company name, contact email, deal size, and status into System B, field by field. Sometimes you catch a typo halfway through and have to start over.

The worst part is when System A goes down right after you've noted which records to transfer. You lose track of where you left off and end up either missing records or creating duplicates in System B.

Before you start.

All of it has to be true, or step one fails in a way that is annoying to debug.

Admin access to both systems or someone who can grant API permissions
Ability to export a sample record from each system to see exact field names
A automation platform account (Zapier, Make, or similar) with connectors for both systems
Write permissions in the destination system for your automation account

The steps.

Export sample records to map your fields
Download one complete record from each system as CSV or JSON. Open both files and identify which fields in System A correspond to which fields in System B. Note any fields that need transformation, like date formats or dropdown values that don't match exactly.
Set up the trigger in your automation platform
Create a new automation and choose your source system as the trigger. Select 'New Record' or 'Updated Record' as the trigger event. Test the connection and confirm it can see recent records from your source system.
03
Configure field mapping with this prompt
In the action step, select your destination system and choose 'Create Record'. Map each source field to its destination field using your export comparison. For any fields that need format changes, use the transformation options in your platform.
Paste this
```
Map these fields from [Source System] to [Destination System]: [field1] to [field1_destination], [field2] to [field2_destination]. Transform [date_field] from MM/DD/YYYY to YYYY-MM-DD format. Set [status_field] to 'Pending Review' for all new records.
```
Handle field validation and required fields
Check which fields are required in your destination system but might be empty in the source. Set default values or use conditional logic to skip records that lack critical information. Test with a record that has missing optional fields.
Add duplicate detection logic
Before creating the new record, add a search step that looks for existing records with the same email address or ID number. Configure the automation to update the existing record instead of creating a duplicate, or skip the action entirely if a match exists.

Set up error notifications with this prompt

Add an error handling path that sends you an email when the automation fails. Include the specific record data and error message so you can fix issues quickly.

Paste this

Send email notification when automation fails. Subject: 'Record sync failed - [Source System] to [Destination System]'. Body: 'Failed to sync record: [record_id]. Error: [error_message]. Source data: [trigger_data]'. Send to: [your_email].

Test with historical records
Turn off the automation and manually trigger it with 3-5 recent records from your source system. Verify each record appears correctly in the destination system with all fields populated. Check that your duplicate detection works by running the same record twice.
Enable and monitor the first week
Turn on the automation and check both systems daily for the first week. Compare the count of new records in each system to ensure nothing is missed. Watch for any records that get stuck in processing or create unexpected duplicates.